ICP just removed a major cryptographic bottleneck:
▪️ 10× increase in Chain Key signing throughput
▪️ 100+ signatures per second burst capacity
▪️ Pre-signatures moved into replicated subnet state
This means:
▪️Faster cross-chain interactions
▪️Better performance for Chain Fusion
▪️Infrastructure scaling for real-world apps
You are underselling canister memory. Replication is only one aspect, can get the same with erasure coding for cheaper. Canister memory: high availability, stored in full directly at the compute nodes, on SSD, can be computed against with low latency in query and update calls. Much more valuable than simple replicated storage.
@gatorbro7890 @zspeccc https://t.co/eqpTAF9qPz is manual coding (an in-browser IDE with deployment function). But you can pick templates to start from that you can modify or even deploy as-is.
If you want no-code from scratch then https://t.co/z4l3g0RAjw is the tool.
@yousay_icp That was a multi-token ledger (not exchange). It has been running for years now, tokens can be created and moved, there's a wallet for it. But only toy tokens because the ledger itself is still centrally controlled. To really launch it we need to figure out the governance of it.
The easiest way for newcomers to experience ICP is by static frontend hosting. On https://t.co/iJAYwSe1tQ you can paste a GitHub URL containing static frontend and get it deployed with 1 click on ICP. No tokens required. Try it now!
Why is it important? Every DeFi frontend needs decentralized hosting. No compromises and no excuses. It's so easy.
Btw, you can host Telegram mini apps, too. Just use the canister URL in your Telegram bot configuration.
Lol. Crypto industry first creates problems that shouldn't even be there in a good design. Instead of fixing the design, it takes the problem for granted and creates a whole new sub-industry to "solve" it. MEV is another example to add to this list.
Wise Men of Gotham.
That said, there are reasons ICP gets suppressed. You’ll notice that if any single ICP feature became widespread, it would essentially wipe out an entire sector of the industry.
Built-in, free oracles—the oracle sector is gone.
Smart contracts can directly sign transactions on other chains—chain-abstraction sector, gone.
Trustless connectivity between any two public chains—the cross-chain bridge sector, gone.
Smart contracts with native, large-capacity storage—data-storage blockchains, gone.
Contracts can directly generate threshold signatures—MPC and embedded-wallet sectors, gone.
The most flexible account-abstraction in the space, able to directly control assets on other chains—AA wallets and multisig wallets, gone.
Transfers are the fastest in the ecosystem with the smoothest UX—high-throughput chain sector, gone.
Reverse gas fees—those touting “use stablecoins to pay gas” as a differentiator, gone.
Full BTC nodes running directly on ICP—the most decentralized and secure BTC integration—BTC L2 sector, gone.
The most advanced identity-based cryptography in the industry—data privacy & encryption sectors, gone.
Native WASM support—making it the best platform for verifying ZKPs; no matter how large the proof, verification costs are nearly zero, and results can be written to any other chain—those assorted ZK tricks invented to work around Ethereum’s limited compute, gone.
A vibe-coding platform whose features and UX are better than those of actual AI companies, with one-click on-chain deployment—the Web3 + AI sector is basically gone too.
The killer part is that ICP would drag the whole Web3 industry from a “tell a story, issue a token, pump, and rug” model back to a “build products, launch for real, and make money” model. No wonder it’s not exactly welcomed. 🤣
@GeorgioDiab@BitWalker_@WorldCloud_IC Awesome, thanks! Btw, notable features of https://t.co/iJAYwSe1tQ : you hold the canisters in self-custody, register custom domains from the dashboard, you can make your frontend immutable with a click.
@xiao_zcloak Btw, a #Zcash on top of #ICP was created in 2022: https://t.co/4lQ04PwE5g https://t.co/2ISJSnQ5MT
Would love to see it revived or your version.
@Narodism Totally agree on the L1's shortcuts. But Safe are highly negligent. They know about the shortcut because they are experts. Yet they design a product that a) hosts its frontend on AWS and b) requires blind-signing on a Ledger Nano. Then they boast that $100b are "secured" with it.
@dominic_w Or configure to make it immutable, i.e. no change to the assets is possible. Provide the next version of the interface in a new canister. Doesn't hurt to keep all old versions around. User can choose which one to run.
@soulasiknowit @Firerisk6 You can send any ck-token back to its native chain. For example ckBTC to a Bitcoin address. ckUSDC's native token is USDC on ETH. So you can send ckUSDC to an Ethereum address but not to Stellar.