There are some thoughts here certainly: Native Autonomi tokens <> ERC20 2-way bridging ideas
Also, bridging was baked into ACT design, which was based on ideas for pre-v1 native token (DAG/GraphEntry), and prepared to become Native Token itself as soon as changes in Node’s source code would be possible without forking (in terms of team/community, not just the code) the project:
# Autonomi Community Token
Autonomi token standard, that enables issuing own token by anyone – from scratch, or by wrapping existing ERC20 tokens.
Token is based on a DAG of transactions represented in the network's storage as instances of GraphEntry data. GraphEntries are connected by *parents* and *descendants* lists. The token comes in two flavors: *Native* and *Bridged*.
We begin with creating library and application for Autonomi, not including changes to API/node code.
## Native ACT
Each graph is a separate token.
Token ID is a xorname of the Chunk containing token info: *symbol*, *name*, *decimals* and address (PublicKey) of genesis spend. This token ID will be different for every new token, even with same symbol, name and decimals.
Genesis transaction GE:
* *content* is token ID
* Empty *parents* (indicating Native genesis transaction)
* Single *output* to issuer's key. This value is a *totalSupply*.
## Bridged (ERC20) ACT
show original
Maybe here?
from – Relatively fast, it’s a question of rather simple smart contract and some code that will execute things. ACT architecture already supports that.
to – That’s less obvious, because that would require oracles for EVM to interact with Autonomi. But at the same time while we are able to bridge other currencies into Autonomi and exchange them internally , a bridge in this direction is perhaps less of a problem?
It’s already there:
Not a sign of this so far.
This would requ…
I’m not lost, just life kicked in. Also, I think I have lots to catch up with, the whole v2 thing is new to me. I love the fact, that the heart of the project is still beating strong here
4 Likes
