57 / Qumosi, 037 question box, Dan's PA Finale

Dan's last PA hurrah! Join the discussion on 2023 predictions, regulation, and NFT mainstream media attention. Delve into the world of dynamic NFTs, avoid the fate of Tornado Cash, and learn about fuzzing smart contracts and ex post facto laws.

Timeline

00:00 Intro

00:41 How to say Qumosi

01:05 2023 predictions

08:37 More regulation

12:06 Crypto/NFT mainstream media attention is...

12:53 Thank you OpenAI for taking the spotlight

15:59 Dynamic NFTs

16:32 Avoid fate of Tornado Cash

20:27 How to fuzz smart contracts?

21:24 Fear ex post facto laws?

Participants

@fulldecent

William Entriken

@dtedesco1

Daniel Tedesco

@magicking_

https://6120.eu

@realsternbauer

???

@VjDeliria

Vj Deliria

@EllieVoxel

???

@t012n4d0

???

@retromort

???

Episode notes

• Qumosi and the code on GitHub

• Qumosi // ??? IPA?? english phonetic thing?
• Predictions
  • 037
    • Regulation
  • VjDeleria
    • Celebrity NFTs
  • Ellie
    • Music NFT mainstream (like getting an iTunes giftcard) see sound.xyz and Snoop Dogg just sold USD 200k on there
  • B2B is touch
  • Gaming
  • ChatGPT / Generative AI will be the main tech story of 2023, not blockchain
  • Thank you OpenAI for taking the spotlight off of blockchain so we can build in peace and quiet
  • Chess cheating: https://www.chess.com/blog/CHESScom/hans-niemann-report
  • @realsternbauer / dynamic NFTs /
    • Cows & trees
    • Pretty close with many consumer goods, requires consumer demand
• Questions from @037: (https://github.com/Qumosi/QMSI/commit/27c5f472dddb02f50d680557688156404152a4af)
• Questions from @037 (misc):
  • When deploying smart contracts with no hard controls to freeze assets, etc. how can we stay compliant to AML and not face jail like Tornado cash dev Alexsey Pertsev while also ensuring users trust us with no “owner” role?
    • See episode about nothing is decentralized: episode 26
    • Don’t see regulators going after technology, but rather how it’s marketed (so far)
  • What are some modern ways to fuzz your custom smart contract code? Are there any good frameworks for security scanning contract code during runtime?
    • Smart contracts best practice is not to use fuzzing, but rather 100% test coverage
  • Are there any ex post factos to pending/future SEC regulations surrounding smart contract development? Could I get in trouble if I deploy something now and then SEC requires a control mechanism that doesn’t exist and cannot be added (since smart contracts are set in stone after deploy)
    • SEC has rules but also //ask// CFTC
• Thank you for staying to the end