on 6529 network it is a non-event, all validators will validate
Context from
david
#47648
2025-03-26 23:11
or is this on the 6529 network we are talking about posting the root hash
on eth
Context from
david
#47648
2025-03-26 23:11
or is this on the 6529 network we are talking about posting the root hash
anyway
though i think most blocks won't post
yeah maybe
Context from
david
#47644
2025-03-26 23:10
so we will be filling up ethereum block space. can't we have a lot of nodes sign a single transaction with the root hash
etc etc
we will see more TDH for the correct root and more validators for the correct root
so let's say you go rogue and post an incorrect root but also 6529 museum and bored and maybe all post the correct root
otherwise it is just a centralized L2
yes! any node with more than [x] TDH can post and more than 1 node can post the same block
Context from
david
#47637
2025-03-26 23:09
you mean the oracle on ethereum? so it will be many nodes that post roots?
that the validators have a built in reputation system
it is very very very powerfulw
we can judge accordingly
given we know their TDH
e.g. more than 1 validator can post block hash for the same block on the oracle
maybe its rule is that "it needs 1M TDH" or 5% of current TDH to authorize
it is just one validator that posted with 100K TDH
it checks the oracle to see if the root on the oracle has that approved transaction
someone tries to push through a "sell 50 of them" tx
on ETH mainnet
6529 research has a wallet with 10,000 meme cards
i mean this
Context from
david
#47624
2025-03-26 23:06
I see you mean as new blocks form in 6529 network with consensus on the root block
and you can bootstrap from there
once you have that, you have initial TDH state
the only trust assumption is that the first transaction is valid (we will do that one)
if you had the 6529 research wallet though maybe you would want to see something like 10% of network TDH has posted the root before you can transact
you can accept any posted root from TDH > x
if you have a lightweight low value wallet
for example
on the oracle
i think the way to manage (I think) is for each smart wallet to decide on what it needs on consensus
it would also monitor ofc the oracle contract
the node hooks up to an RPC and monitors our NFT contracts
TDH calculation
this is the first thing we will release in the Go nodes
the blockchain nodes will monitor transactions on the supported chains yes
Context from
david
#47606
2025-03-26 23:02
will the clients run a node on each chain supported to verify the correct merkle is stored on that chain. or maybe all they have to do is poll the other networks and check
so we should use our reputation system for this
an ETH tx
LINK does many things but in this case we only need one thing
from our perspective
from LINK
which is all the Oracles are doing
than "do a transaction on ETH"
and since it is harder to build a reputation system
it is like LINK had hundreds of operators and we had a full reputation system built around them
TDH, rep, identity, etc
and for which we have very rich information
that know the root
we will have dozens / hundreds / thousands (?) of validators
here you don't have 1-2-3 operators that know the root