Q&A with Chainlink, Alchemy, and Truffle
summary
Chainlink explains using the on-chain feeds registry vs ENS for consistent oracle addresses; multi-field responses fit arbitrary bytes so use cases include storing an IPFS CID large responses or multiple JSON attributes, limited only by transaction size. Alchemy describes Supernode and a voxnodey democratic selection algorithm that picks the latest block from a cohort of nodes for data correctness. Truffle outlines Truffle DB with a Truffle DB hosted instance option, Ganache forking behavior and pending-tx modes, TypeScript migration, and OpenZeppelin upgradeable integration.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:30Feeds Registry
- 2:00Hardforks
- 3:00Data correctness
- 4:00Decentralization
- 5:40Large Responses
- 7:35Where do the records get kept
- 8:35Best practices
- 9:20Feedback from the community
- 10:45Feedback from Nick
- 11:30Pending transactions
- 12:25ganache v7
- 13:15Multichain a year from now
- 14:00Upgradeable contracts
- 15:00Typescript support
- 16:00What to do after the conference
