Subscribe to julieshi.eth
julieshi.ethNote on Moonshot Hackathon 2022 - Tina's Panel on "How to make a pitch deck"
Pitch Deck平均投资人花2min44秒看pitch deck可以录一个pitch视频，大概5min，方便投资人看Classic structure of a pitch deck?Screenshot of the panelWhat’s the underlying problem you wanna solve?Why are you the best person to solve this problem? 以Solana 为例，前Qualcomm的经历。这些structure的priority是什么？Tina：每个fund都有不同的preference。注意就是每个team其实都有strength和weakness，that’s ok。Airbnb市场要比reasonable but also bold。把market potential要写清楚 - 要把很宏大的未来表述出来，新兴technology很小但是growth 很快。商业模式 - web3项目不太讲商业模式；但是投资人比较实际。Competitor Analysis - 预见secondary com...
julieshi.ethPotter meeting Note June 7th
Key Takeaway & Thoughts:关于Gas fee 以及social feature - 我们现在对一些web3 native的tool还不了解导致把dev的解决方案想复杂/不natural了，像Idriss.xyz, biconomy.io, EPNS 可以解决我们的技术需求，在开发遇到阻力的时候需要多思考，多借力。新的用户需求值得思考：web3 还是个圈子 - 很多人都在going after看接下来有什么大型活动、有什么after party，但是缺乏一个aggregator - that’s something we can solve - 可以先去拉取Eventbrite等有质量的web3 Event。手机版的不必要开发，等融了钱可以去开发。Better goal：UI定下来电脑版开发的。Deck结构:Logo - one-linerBackgroundIRL - web3 割裂：web3 在mobile app的普及率；缺少infra去connect IRL 活动和web3 身份CyberConnect的逻辑：build web3和社交图谱TokenP...
<100 subscribers
julieshi.ethNote on Moonshot Hackathon 2022 - Tina's Panel on "How to make a pitch deck"
Pitch Deck平均投资人花2min44秒看pitch deck可以录一个pitch视频，大概5min，方便投资人看Classic structure of a pitch deck?Screenshot of the panelWhat’s the underlying problem you wanna solve?Why are you the best person to solve this problem? 以Solana 为例，前Qualcomm的经历。这些structure的priority是什么？Tina：每个fund都有不同的preference。注意就是每个team其实都有strength和weakness，that’s ok。Airbnb市场要比reasonable but also bold。把market potential要写清楚 - 要把很宏大的未来表述出来，新兴technology很小但是growth 很快。商业模式 - web3项目不太讲商业模式；但是投资人比较实际。Competitor Analysis - 预见secondary com...
julieshi.ethPotter meeting Note June 7th
Key Takeaway & Thoughts:关于Gas fee 以及social feature - 我们现在对一些web3 native的tool还不了解导致把dev的解决方案想复杂/不natural了，像Idriss.xyz, biconomy.io, EPNS 可以解决我们的技术需求，在开发遇到阻力的时候需要多思考，多借力。新的用户需求值得思考：web3 还是个圈子 - 很多人都在going after看接下来有什么大型活动、有什么after party，但是缺乏一个aggregator - that’s something we can solve - 可以先去拉取Eventbrite等有质量的web3 Event。手机版的不必要开发，等融了钱可以去开发。Better goal：UI定下来电脑版开发的。Deck结构:Logo - one-linerBackgroundIRL - web3 割裂：web3 在mobile app的普及率；缺少infra去connect IRL 活动和web3 身份CyberConnect的逻辑：build web3和社交图谱TokenP...
Share Dialog
Share Dialog
It’s tedious to upgrade the code when the smart contract is updated. So here are the steps one can follow when updating the code base. (Hopefully, this pain can be gone later)
Always go to this thread to check jefflau.eth’s post about the update of namewrapper.
https://discuss.ens.domains/t/namewrapper-updates-including-testnet-deployment-addresses/14505
As of today (Mar 19), the latest namewrapper address is 0x114D4603199df73e7D157787f8778E21fCd13066.
Our contracts constructor is based on the namewrapper contract address. As a result, we need to first redeploy our contracts.
Take m3mber as an example, let’s go to:
./contracts/scripts/deploy.js
we need to first change LATEST_ADDRESS to the latest namewrapper address:
const subdomain_reg = await NaiveSubdomainRegistrar.deploy(LATEST_ADDRESS);
Then cd .. i.e. go to ./contracts then type in terminal
$> npx hardhat compile
$> npx hardhat run scripts/deploy.js --network goerli
Contract deployed to address: CONTRACT_DEPLOYMENT_ADDRESS
$> npx hardhat verify --network goerli CONTRACT_DEPLOYMENT_ADDRESS
Note CONTRACT_DEPLOYMENT_ADDRESS is the real address that our contract has been deployed to.
Verify the deployment on https://goerli.etherscan.io/address/CONTRACT_DEPLOYMENT_ADDRESS Keep a record of it so it will be used in step two.
Pro tip: if it’s deployed & verify successfully, there should be a little check mark on contract
To correctly call the smart contract, we not only need the smart contract's address, but we also need its ABI.
Our ABI files are all saved in a directory. Go to m3mber/lib and see all the ABI json files in it. For our current update, you need to update the ABI file of
m3mber-registrar-abi-goerli.json
This address is the address of the contract that you deployed in step 1
ens-resolver-abi-goerli.json
You need to look up the right contract address step 0
namewrapper-abi-goerli.json
You need to look up the right contract address step 0
To access a contract’s latest ABI, go to https://goerli.etherscan.io/address/ADDRESS then click the contract tab, scroll all the way down, and you will see:
Click the copy button - then you get the ABI of that address, then paste it to the correspondent file.
Go to lib/constants.tsx and update
export const M3mberRegistrarAddrGoerli = LATEST_ADDRESS_DEPLOYED_ON_STEP_1
export const namewrapperAddrGoerli = LATEST_ADDRESS_ON_STEP_0
export const ensResolverGoerli = LATEST_ADDRESS_ON_STEP_0
🎉 Yay you are done! You just finished the step of upgrading the files~
It’s tedious to upgrade the code when the smart contract is updated. So here are the steps one can follow when updating the code base. (Hopefully, this pain can be gone later)
Always go to this thread to check jefflau.eth’s post about the update of namewrapper.
https://discuss.ens.domains/t/namewrapper-updates-including-testnet-deployment-addresses/14505
As of today (Mar 19), the latest namewrapper address is 0x114D4603199df73e7D157787f8778E21fCd13066.
Our contracts constructor is based on the namewrapper contract address. As a result, we need to first redeploy our contracts.
Take m3mber as an example, let’s go to:
./contracts/scripts/deploy.js
we need to first change LATEST_ADDRESS to the latest namewrapper address:
const subdomain_reg = await NaiveSubdomainRegistrar.deploy(LATEST_ADDRESS);
Then cd .. i.e. go to ./contracts then type in terminal
$> npx hardhat compile
$> npx hardhat run scripts/deploy.js --network goerli
Contract deployed to address: CONTRACT_DEPLOYMENT_ADDRESS
$> npx hardhat verify --network goerli CONTRACT_DEPLOYMENT_ADDRESS
Note CONTRACT_DEPLOYMENT_ADDRESS is the real address that our contract has been deployed to.
Verify the deployment on https://goerli.etherscan.io/address/CONTRACT_DEPLOYMENT_ADDRESS Keep a record of it so it will be used in step two.
Pro tip: if it’s deployed & verify successfully, there should be a little check mark on contract
To correctly call the smart contract, we not only need the smart contract's address, but we also need its ABI.
Our ABI files are all saved in a directory. Go to m3mber/lib and see all the ABI json files in it. For our current update, you need to update the ABI file of
m3mber-registrar-abi-goerli.json
This address is the address of the contract that you deployed in step 1
ens-resolver-abi-goerli.json
You need to look up the right contract address step 0
namewrapper-abi-goerli.json
You need to look up the right contract address step 0
To access a contract’s latest ABI, go to https://goerli.etherscan.io/address/ADDRESS then click the contract tab, scroll all the way down, and you will see:
Click the copy button - then you get the ABI of that address, then paste it to the correspondent file.
Go to lib/constants.tsx and update
export const M3mberRegistrarAddrGoerli = LATEST_ADDRESS_DEPLOYED_ON_STEP_1
export const namewrapperAddrGoerli = LATEST_ADDRESS_ON_STEP_0
export const ensResolverGoerli = LATEST_ADDRESS_ON_STEP_0
🎉 Yay you are done! You just finished the step of upgrading the files~
No comments yet