You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

61 lines
2.1 KiB

  1. ---
  2. layout: simple
  3. base: '../'
  4. ---
  5. # Design Notes
  6. ## Initial design choices
  7. - protocol/routing/network layer: websockets (multi nonblocking clients)
  8. - server-side fileformat : yaml
  9. - client-side fileformat : JSON
  10. ## Language choice:
  11. serverside: perl (or nodejs)
  12. clienside: javascript
  13. ## block chain structure
  14. minimally sized blocks :
  15. - segreated signature, timestamp, audit etc.
  16. - block: {address, previous, pow}
  17. - use balances for state rather than TXO to avoid the need keep txo states, and link txi to utxo
  18. ## observation ...
  19. - revokable block if sign w/ a DH on txo and ECDSA on txi
  20. - txroot (merkle root can be global)
  21. - PoW is to slow down chainupdate to avois spam
  22. - consensus is on the longest length
  23. - /!\ maximal work is hackable (as pow is exponential to difficulties)
  24. - sort of tx sequence can be done on node side
  25. - block chain can store tx out of order (FIFO style)
  26. - does mining really need to be conpetitive ?
  27. - if mining is done by all node the recipient of txo will be willing to mine!
  28. - if a .2% tax on transaction can replace/solve all VAT taxes
  29. then mining rewards is "artificially" inflated to compensate for a wasteful
  30. technology
  31. - nano-trading is stealing (i.e. taking advantage of who has the power to be informed fast)
  32. on need to put a "lowpass" filter on trading :
  33. speculation is necessary for long term protection against future uncertainty...
  34. short term predicition make no sense !
  35. long unpredictable queue time (mempools) can deter speculator as it would be like "lotery"
  36. lotery is a "gamified" tax extractor.
  37. - PoW can be replaced by ZK proof of some Work
  38. - should it be txo which carries the burden of proof of work ?
  39. - validator already do a great job making the system "alive"
  40. - block reward could be proportional to the number of tx in the block i.e. the "real" work is indeed the verif not a hash-puzzle
  41. - How to mitigate DDoS on Mempool ?
  42. -
  43. - why would we want making block more and more difficult to add when technology advance ???
  44. (how to make spice of spamming constant through technology ?)