Pinned Tweet
🎊 ink! on PolkaVM is finally here, and in partnership with @joinwebzero the The Blockspace Synergy Hack at the @Web3summit gave us our first glimpse at what’s possible on @Polkadot. 🚀
This hackathon brought all the good developer vibes ✨
The journey has begun. 🧵
💜
And who could forget when we played the @ink_lang game at @AcademyPolkadot??
It was the BEST way to introduce and teach smart contracts and get students hands on experience quickly!
omg and when Dima turned the team all into NFTs??
damn, maybe gone, but def not forgotten❤️🩹
ALT Teaching smart contract module in Berkeley
ALT My first ever cartoonified Lolocoding NFT! Thanks ink! 🦑
ALT When the BeReal would hit mid class 🤳
ink! retweeted
long live ink! 😢
The best team I worked with at @paritytech
Exceptional engineers, thoughtful humans, deeply committed to the ecosystem, the builders, and developer experience.
Grateful for what I learned the @ink_lang team.
ink! retweeted
When I first met you in 2022 at PBA, you were still part of parity. The uniqueness could be found in every small details. It was hard to write real apps with ink first. But it became better and better. And in fact one of the few reasons to be on Polkadot were rust smart contracts
Goodbye. All the best to the developers who created maintained and sweated ink
We believe the community deserves a full, transparent account of:
• what happened
• why decisions were made
• what this means going forward
That context is shared in the forum post below.
Thank you to everyone who built with ink!, contributed, reviewed, asked hard questions, supported the work, and shared our passion.
We wish everyone well. All the best.
Forum Announcement
👉 forum.polkadot.network/t/dis…
ink!: Status, Context, and Why It Matters for Polkadot
We’ve published a detailed update covering the current state of ink!, recent progress, ecosystem impact, and the risks ahead.
forum.polkadot.network/t/ink…
Why You Should Use Ethereum Addresses Inside Your ink! Contracts
PolkaVM and its precompiles operate on H160 addresses. While testing a contract interacting with the erc20 precompile we ran into a small but important detail that ink! developers should keep in mind.
If you take a Polkadot AccountId32, convert it into an H160, and then send tokens to that H160 without explicitly mapping it through revive, the runtime will not credit the original Polkadot account but a fallback account derived from that H160.
Nothing errors but the tokens end up in the fallback account, not where you expected. Retrieving them requires revive-specific recovery extrinsics an inconvenient extra step for both users and developers.
The simplest way to avoid this is: Use Ethereum H160 addresses as your contract’s identity format.
ink! retweeted
Polkadot Builder Party Hackathon: The Winning Projects xitter.cf/i/broadcasts/1eaKbjVaW…
