Sub-pages
| Child pages (Children Display) |
|---|
FAQ
The foundation does not want to be a point of focus
The main goal is to get tokens and domains to the Ethereum chain
Decentralization is important, but we could do a non-foundation single point of failure (BP) with proper mechanisms in place
Approval should be a multisig solution
Links
...
Component
...
Code
...
Wiki
...
Alien Teleport
FIP: https://github.com/
...
...
...
...
DEV Environment:
fio.oracle and oracle server: http://
...
fio.wrapping
...
...
Oracle
...
ETH contract
Dashboard: http://44.234.122.169:8000/
Ropsten endpoint: http://50.250.156.58:18545/ or ws://50.250.156.58:18546
dApp to interact with contract: https://oneclickdapp.com/matrix-second
contract address: 0x409F0d72e4700884200df4B11394b10A3539EB94
oracle: 0x41D1ADa8F67968F54Dbc55a259302dE700bC2bE9
Github
fio.oracle Oracle code(on blockpane)
fio.oracle FIO contract branch: https://github.com/
...
...
...
Key Assumptions
The main goal is to get FIO tokens and domains to the Ethereum chain.
The foundation does not want to be a point of focus.
Decentralization is important, but we could do a non-foundation single point of failure (BP) with proper mechanisms in place.
Approval should be a multisig solution.
Oracles will be paid in FIO. Paying in WFIO will not work because with NFTs there is no WFIO involved.
We are using a network of independent Block Producers to manage the Oracle instead of a WBTC “merchant” approach is for regulatory reasons. The Foundation does not want to take the regulator risk.
It is not likely that users will be wrapping small amounts of FIO, so this lessons the impact of high fees. If it is whales moving FIO, the fees will be less of a concern.