meowsbits
commented
2 years ago cc @ziogaschr
- What is "AHA transactions"? you refer to "AHA/TABS"? is the anchestor hash in HFC? add it in glossary
Ancestor Hash Appended transactions. AHA/TABS is both. TABS softly requires some kind of scheme to achieve segment-specificity (aka chain exclusivity) for transactions, which AHA does.
- reading balances from state, is this a problem with levelDB for clients?
Light clients won't be able to validate the field, but light client already can't validate state stuff, like stateRoot.
Otherwise, for normal clients, this should not be a problem, though it will require a few more milliseconds.
Geth removes transactions indexes by default now for past blocks, but for TABS we'll only need to read balances at the parent height of the block we're validating. If the client can validate the state root, they should be able to read the balances for the a subset of the touched accounts for the block.
- what happens when a new account (without balance) sends a TX in a full network? will miners prefer others?
Well, let's say the new account has a low balance, but non zero. They'll need some balance to pay for gas probably. In order to avoid a Balance Poisoning attack, miners will need to prefer transactions by balance to some extent, but probably not exclusively. Transactions with greater balance will improve their chance of producing a canon block, but the demand for transactions by balance will have a ceiling of immediately diminishing returns; once they beat the parent block's TABS score, there's no incentive to push the TAB score higher, and they can sort by gas fees again.
- does TABS affects the pools? as each pools' miner has its own balance?
Pools, like solo miners, still need to use a single account as the coinbase for mined blocks.
- will a pool that is able to attract the richest miners be able to manipulate the network?
First, note that we'll consider the aggregate balances of transactions constant; they can be uesd in any block regardless of the miners. Less the transactional balances, the miner balance will be the decisive score between blocks. And indeed, richer miners will win more blocks than poorer miners. We (will) show that extra win margin for richer miners is actually pretty low. TABS's role in the consensus scoring is basically to break difficulty ties that happen for near-simultaneous blocks.
- Ancestor Hash vs. Chain ID: if later we think of changing that, this might cause trouble in tooling, like metamask, remix, etc (but dealable)
We're not proposing to replace Chain ID, for that very reason. But we'll still need to do some dealable work to add the AHA field to the tooling you mention. The good news is we don't have to invent any patterns, only add a field. The chain/transaction tooling patterns already query blockchain state to get info like tx nonce, so we'll just need to piggy back on that.
- does TABS counts the balance before or after the TX execution? (I read this I think, but can't find it now)
Before. For simplicity's sake, it uses the balance of the address at the parent block.
ziogaschr
Questions by @ziogaschr