meeting summary
gas table
- adopt Gas cost for precompiles proposal with tweaks
- spawn (updating 2 accounts) is more expensive than self-spawn (updating 1 account)
- gas for multisig accounts (1/k, 2/k, 3/k) should be a function of k
- 1000 smidges / gas unit to allow for more granularity
- at genesis, smapp set minimum gas price to 1000 smidges (configurable) and miners will not accept txs lower than this minimum gas price
- use first-price auction (miners select txs with highest gas price) for genesis (already implemented). but this is not the end-game. it will need to be adjusted post-genesis.
- AI:
- Dmitry create issues for implementations for the proposal
genesis ID
- use unix timestamp (uint64) instead of timestamp string literal.
- genesis data contain some last-minute revealed data like bitcoin block hash
- golden atx use the original 32 byte hash instead of hash32->hash20->pad0
- AI:
- Dmitry already made PR
discussion on vm design
- ppl ARE on the same page wrt spacemesh-specific L1/L2 separation
- AI:
- Iddo follow up on discussion with Dmitry about evm compatibility
use fixed-precision math in consensus code
- it is a GO
- almost spec’ed in use fixed precision math in consensus code · Issue #4268 · spacemeshos/go-spacemesh · GitHub
- issuance requires logarithmic library, use its own library which internally use big.Int. should be changed when there is a 2nd impl of spacemesh client
- AI:
post update path
- some params don’t require network-wide re-initialization (k2)
- change to N iteration will require re-initialization
- by design, difficult can be adjusted by reducing label size from 16 byte to <1 bit per label (a.k.a labelsperbit). but this is not currently supported
- delay the discussion on update path after more info on Vulcan bug fix (multiple fronts)
- AI:
- do nothing
post param
- unit size 64 GB, min unit size 4.
- there is a gap btwn theory and actual data. for adversary that choose to store 70% of data, the chance of failure should be 99.9%, but is not according to Bartosz data. for K1-279, K2=300, adversary only needs 21K nonces, while it should be 1million nonces
- segment size of AES output selection
- launch test net with K1: 279, K2: 300, K3:65 to make it difficult for re-calculating
- AI:
- Iddo follow up discussions