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.

49 lines
1.4 KiB

  1. # Design Notes
  2. ## Initial design choices
  3. - protocol/routing/network layer: websockets (multi nonblocking clients)
  4. - server-side fileformat : yaml
  5. - client-side fileformat : JSON
  6. ## Language choice:
  7. serverside: perl (or nodejs)
  8. clienside: javascript
  9. ## block chain structure
  10. minimally sized blocks :
  11. - segreated signature, timestamp, audit etc.
  12. - block: {address, previous, pow}
  13. ## observation ...
  14. - revokable block if sign w/ a DH on txo and ECDSA on txi
  15. - txroot (merkle root can be global)
  16. - PoW is to slow down chainupdate to avois spam
  17. - consensus is on the longest length
  18. - /!\ maximal work is hackable (as pow is exponential to difficulties)
  19. - sort of tx sequence can be done on node side
  20. - block chain can store tx out of order (FIFO style)
  21. - does mining really need to be conpetitive ?
  22. - if mining is done by all node the recipient of txo will be willing to mine!
  23. - if a .2% tax on transaction can replace/solve all VAT taxes
  24. then mining rewards is "artificially" inflated to compensate for a wasteful
  25. technology
  26. - nano-trading is stealing (i.e. taking advantage of who has the power to be informed fast)
  27. on need to put a "lowpass" filter on trading :
  28. speculation is necessary for long term protection against future uncertainty...
  29. short term predicition make no sense !
  30. long unpredictable queue time (mempools) can deter speculator as it would be like "lotery"
  31. lotery is a "gamified" tax extractor.