[FIP-17.b] FIO Domain Wrapping
[FIP-17.b] FIO Domain Wrapping
Sub-pages
Key Decisions
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.
Links
Component | Code |
---|---|
Wiki | |
Alien Teleport | |
fio.wrapping | |
fio.erc721 | |
Oracle |
|
ETH contract |
, multiple selections available,
Related content
FIO Domain Wrapping Operations Manual
FIO Domain Wrapping Operations Manual
Read with this
[FIP-17.a] FIO Token Wrapping
[FIP-17.a] FIO Token Wrapping
Read with this
FIO Token and Domain NFT wrapping
FIO Token and Domain NFT wrapping
Read with this
Allow FIO Domains to be mapped to DNS record
Allow FIO Domains to be mapped to DNS record
More like this
Domain Wrapping
Domain Wrapping
Read with this
FIO Governance Improvements
FIO Governance Improvements
More like this