W3

Three Web World

Ideas

NFT Mass Adoption

1. three components
   1. sustainability and energy efficiency
   2. NFT infrastructure 2.0
      1. native
      2. advanced right management
      3. customizable
      4. multi-source
      5. dynamic
      6. fractional
   3. new use cases
      1. event tickets
      2. loyalty programs/community building/reputation
      3. physical products
      4. identity
      5. real restate
      6. refungible

      7. memorial

         Intersection of AI and Blockchain

2. code generation
3. code test
4. code audit
5. trading bot
6. mature automation

7. intelligence focus

   BRC69

8. recursive inscription
   1. inscribing images of traits onchain
   2. inscribing BRC69 collection deployment json
   3. inscribing BRC69 collection javascript compiler
   4. inscribing BRC69 asset with the mint operation
9. bitcoin ordinals
   1. ordinal protocol
      1. fundamental unit
      2. inscribing digital assets
      3. inscribe data into witness of transaction
   2. bitcoin as a secure and decentralized network for data storage
   3. ordinal
      1. conventional arguments
      2. inscribing data into block space
      3. efficient arrangement of data in transaction

      4. statoshi position: four distinct parameters

         AI

10. mechanical engineering versus software engineering
11. passionate about what you are doing
12. spiritual pursuit
13. believe so hard in what you are doing
14. There is always a different way.
15. ask the right questions
16. build with reality

17. foundation model and your own model

    Ethereum

18. blockchain technology beyond currency
19. opcodes instructions
20. account address controlled by private key
21. contract address controlled by contract code
22. code execution

zysync

1. use zksnark to scale up. transaction
2. switch from privacy to scale up
3. knowledge proof: snark and stark
4. main chain as witness of state and side chain for transaction process
5. off chain computation
6. execute state transition functions correctly
7. data availability
8. transaction executed by evm
9. reconstruct the state
10. history and state

zksync

1. float history
2. many nodes in the merkle tree
3. transaction: generic transaction, balance transfer, program
4. proof verification and data availability
5. different storage space between layer1 and layer2

Innovation

1. DePINs
2. scroll zkevm
3. native layer2 code

4. migrate from layer1 to layer2

   scroll zkevm

   1. intersection hardware and software
   2. acceleration proof
   3. advanced crypto algorithm
   4. compiler
   5. general purpose
   6. uniswap on testnet
   7. bridging between layer2 and layer1
   8. evm circuit as a whole
   9. compile evm down to local virtual machine
   10. same environment support
   11. sequence implementation
   12. private GPU cloud/cluster

   13. decentralized proof generation

       Ethereum protocol

5. client
   1. go
   2. java
   3. C#
6. node
   1. full node
   2. light node
   3. archival node

7. network

   Layer2 network

8. level up and collect coins
9. application specific blockchain
10. user experience gets better every 6-12 months, so it is better to have a long bear market
11. patience is virtue

12. Ethereum is unfriendly with ZK proof.

    Good culture requires:

13. documentation: writing things down
14. clear communication
15. value accrual

lesson learned

1. more than one implementation for the open protocol and ensure security and flexibility.
2. mission push instead of people push

Cairo

1. intermediate representation: sierra
2. assembly language
   1. fit well with ZK proof
   2. prove purpose
3. cairo vm
   1. field element
   2. generic type
   3. linear type system