Over the past 2 years, I have worked with many startups (Pre-seed, seed, and series A). The difference that made them successful or unsuccessful is the founders and their chemistry. The team can be updated or the product can evolve, but the founders and their working style can't.
FoundersI wrote a tutorial on how to build a private payment system using INCO Network. Inco network is an EVM Layer-1, utilizing fully homomorphic encryption (FHE) to enable composable and operable confidential states. https://aayushguptaji.hashnode.dev/build-a-private-payment-system-using-inco-network
I wrote a tutorial on how to build a private payment system using INCO Network. Inco network is an EVM Layer-1, utilizing fully homomorphic encryption (FHE) to enable composable and operable confidential states. https://aayushguptaji.hashnode.dev/build-a-private-payment-system-using-inco-network
fheOne day, I will start an anon account and rant the shit out on the web3 protocols docs
Ethereum
Has anyone worked on comparing different cross-chain messaging protocols? Like comparing Chainlink CCIP, Omnichain, LayerZero, Wormhole, Entangle, etc. And what criteria should I check to select the right protocol to use for a production-level dApp?
EthereumTo all the Foundry wizards, I need your help with this. I am trying to do mainnet fork testing but am encountering an error. The strangest thing is, it works with DAI but not with WETH. I have provided a detailed description in the Github issue. https://github.com/foundry-rs/forge-std/issues/512
Foundry
I have a security concern. Couldn't someone create a malicious frame where, by clicking, you inadvertently give them control of your wallet and risk getting rugged? Or are there security measures in place to prevent this? @farcaster @farcasteradmin.eth
frameshttps://warpcast.com/aayush/0xa24de5c5 Amazing work 👏 🙌
https://fc-threads.vercel.app/thread/d6266723-5d02-4711-9ada-9748b653e73b
That's it! You'll now receive alerts for all activity carried out by this address. Thanks to QuickNode QuickAlerts.
- Set the expression as "dHhfZnJvbSA9PSAxQ0tWc3pEZFVwNHltR2NlQVpwR3pZRWZyNFJQTkhZcWFNIHx8IHR4X3RvID09IDFDS1ZzekRkVXA0eW1HY2VBWnBHellFZnI0UlBOSFlxYU0=" which is the base64 encoded value for the following expression tx_from == 1CKVszDdUp4ymGceAZpGzYEfr4RPNHYqaM || tx_to == 1CKVszDdUp4ymGceAZpGzYEfr4RPNHYqaM
5. Using the destination ID you created in step 4 above, create a notification on Bitcoin mainnet using the REST API call https://quicknode.com/docs/quickalerts/rest-api/notifications/quickalerts-rest-create-notification - Set the network as "bitcoin-mainnet"
Telegram bot: https://quicknode.com/guides/quicknode-products/quickalerts/nft-telegram-bot Email bot: https://quicknode.com/guides/quicknode-products/quickalerts/emails-for-ens-registations SMS bot: https://www.quicknode.com/guides/quicknode-products/quickalerts/sms-for-token-transfers
Prefer to receive the notifications at a different location? follow the guides below Twitter bot: https://quicknode.com/guides/quicknode-products/quickalerts/how-to-track-uniswap-liquidity-pools-using-quickalerts-and-twitter Discord bot: https://quicknode.com/guides/quicknode-products/quickalerts/nft-discord-bot
4. Use this REST API call to create "destination", this is where you'll configure the URL you want to receive webhooks to https://www.quicknode.com/docs/quickalerts/rest-api/destinations/quickalerts-rest-create-destination
1. Go to http://QuickNode.com and create an account 2. Click on the profile icon on the top left and click on "API keys" 3. Create an API key with access to QuickAlerts REST API
As BitwiseInvest's Bitcoin ETF publicly reveals its address, a move that deserves appreciation. You can now monitor the wallet's activity using @QuickAlerts QuickAlerts, whether for fun, security, or potential gain. How, you ask? Let me explain. 🧵 https://x.com/BitwiseInvest/status/1750224060620111912?s=20