Hi Everyone. I’ll be hosting the 2nd Autonomi Developer Council call will be tonight at 2100 UTC on Jitsi meet. Basically just a place for live conversations about all things Autonomi development. Hope to see some folks there!
4 Likes
Had a great call with @riddim , thunderboltkid, and @bytes this evening. Lots of talk about Autonomi: multi-sig BLS keys, network performance, native token feasability, and current IF projects. And all sort of other topics from traffic nightmares in Mexico City, Canadian armed forces, to the history of Cisco. I’m sorry I had to drop after 2 hours, but I had to eat dinner! Thanks again guys for calling in, hope to talk to everyone again next week.
8 Likes
It’s great to see developers learning & exploring Autonomi together. I hope this call grows in participants as more devs get onboard with Autonomi.
On native token feasibility, was there any kind of agreement on how feasible it’s currently considered?
4 Likes
I think it’s safe to say that validating the DAG and knowing which incoming TX to trust and which one not has been considered one of the greatest (if not the greatest) challenge when it comes to a DAG based native currency … considering TX cost and speed I think it’s safe to assume that the DAG might grow at least as fast as the ETH blockchain … will there be public validators or is everyone assumed/expected to download data ~size of ETH blockchain to make sure the incoming TXs are trustworthy …? if there are public validators what makes them trustworthy? … do we not need validators because nodes only accept TXs that are valid anyway? what do we do on data forks (I think it has been mentioned that they can exist even for e.g. graphEntry; they really appeared at one point in Beta too and it caused the faucet to fail iirc)? what do we do if someone managed to introduce a graphEntry that should not exist how do we get rid of that invalid branch again?
… more questions than answers for now I guess …
but I’m not the greatest blockchain/DAG expert - so 
ps: especially with TXs (creating a GraphEntry) just costing cents or maybe even less that raises the question how many hops are needed for validating 
… if put costs for 1000 hops are at 10 USD (I am not sure those numbers have anything to do with real graphEntry cost 
) that would require at least 10_000 checked hops for a incoming TX of value 100 USD … (and that assumes prices have never been lower … )
6 Likes