Letztes Thema vor 6 Std.

Internet Computer Developer Forum Forum

forum.dfinity.org

Discourse-Forum auf Englisch. 6 beobachtete Rubriken: Community Tutorials & Video, internet-identity, Developers, Rust, Showcase und SNS Framework.

Diskussionen pro Tag
9
Eingesammelte Diskussionen
195
Beiträge pro Tag
44
Rubriken
6
Beobachtete Quellen
8
Software
Discourse

Neueste Diskussionen

Alle 4 Stunden aus dem öffentlichen Feed des Forums eingesammelt. Wiedergegeben werden nur Titel, Link und der Anfang der Nachricht; jeder Link führt zur Quelle zurück.

Native app login flow for Internet Identity

ICRC-167 is a wonderful piece of work. Thank you very much for creating this. If you are looking for a Swift library, I implemented something like this to contribute to the IC. https://github.com/humandebri/ICNativeClient

Hyperliquid Preps in Plug Wallet

Plug wallet has Hyperliquid perps. It has ICP there too, if i want to test how well it works, it gives me exchange rate 10 ICP (27usd) into USD what is worth only 5.9 usd. How can anyone use this if someone is taking so huge cut. Is there a liquidity issue on Hyperliquid side or what is the issue that we get so bad exchange rate.

Native app login flow for Internet Identity

If that understanding is correct, then the main remaining gap for Flutter is no longer an Internet Identity protocol limitation, but rather the absence of a Dart/Flutter implementation/library for ICRC-167 + ICRC-34. That’s correct indeed, it does strictly rely on the universal link mechanism in iOS and Android to land back into the app from a web URL. Is direct ICRC-167 + ICRC-34 now the recommended architecture for a native Flutter application? I’d recommend it with the universal link mechanism yes. Combining that with e.g. AuthTab/CustomTab on Android should result in a single flow user experience. Would you recommend removing the web bridge entirely rather than using @icp-sdk/auth as an intermediary? I’d indeed recommend removing the web bridge entirely, it’s no longer needed with ICRC-167. Is there any work planned on a Dart/Flutter library or reference implementation for this transport? On the web there’s now two libraries that stack one another: @icp-sdk/signer and @icp-sdk/auth . The former implements all the transports and standardized JSON-RPC messages, it’s used by the latter (which also manages auth state storage) to communicate with II and also by apps to communicate with wallets e.g. OISY, Plug, NFID etc. We currently do not have official libraries for other platforms besides web, we’d like to look into mobile support by either documentation and/or library efforts but haven’t been able to prioritize this yet. In practice a whole IC mobile stack would differ sign

Aegis Launchpad — a reserve-backed meme launchpad built natively on ICP canisters

Hi everyone, I’ve been following ICP closely for several months now, and the more I dig into it, the more convinced I am that this is one of the chains with the strongest potential for a real comeback — not on hype alone, but on the actual technology. Reverse gas, canister smart contracts, on-chain frontends, tamperproof HTTP outcalls: this is genuinely forward-looking infrastructure, and most of it still feels underexplored relative to what it can do. But technology alone doesn’t bring a chain back — volume does. A comeback needs real, frequent, organic activity: people showing up daily, transacting, holding a reason to come back tomorrow. And if there’s one category in crypto that reliably generates exactly that kind of high-frequency activity, it’s meme launchpads. That’s the opportunity I think ICP is sitting on and hasn’t fully tapped yet. One thing in particular clicked for me: canisters aren’t just “smart contracts with extra steps” — they’re full programs with their own state, their own lifecycle, and the ability to be the market instead of just settling trades for one. That’s exactly the property a launchpad needs if you actually want to close the usual rug-pull loopholes instead of patching them after the fact. On most chains, a launchpad is a website talking to a contract on someone else’s DEX — kill the site or list elsewhere, and every protection built into the UI is gone. On ICP, the market itself lives in the canister. There’s no “somewhere else” to list to. Th

🚀 Introducing Boxa from BoxaFoundation: Bitcoin, But With One More Layer

nowander I forgot to add your names, to hard to remember and to pronounce @SumMonsterism Why don’t you use your actual names SumMonsterism: you are representing a project I deas i write here represent me as an individual any thing for the project carry the office at the bottom like ~ceo Doxa Foundation

Dogecoin < > ICP Integration : live (beta) :tada:

it is such a shame that all the dfinity grant money got spent before stuff like this was possible. Imagine incentivizing devs to build a whole Dogecoin DeFi ecosystem? Instead, we’re nearly a year on and there isn’t even a DEX pair for ckDOGE.

🚀 Introducing Boxa from BoxaFoundation: Bitcoin, But With One More Layer

man I at first i thought it was doxa by doxa foundation @Dionysus What do you think of boxxa, @Travka and @Henn91 are mostly likely to shoot at you thinking its another doxa project , Wait and see, bad thing i hv cleared air otherwise u would see. I dont know whether i took there wives to fight me like this

195 Diskussionen eingesammelt seit 1 September 2026. Dieses Forum nach Stichwort beobachten →