ICP ecosystem is in dire need of a wallet with a very good experience, PLUG wallet is too laggy, can you speed up the development progress?
Well, have you looked at the commit history of OISY and the related repos? The number of commits and reviews we’ve delivered in the past few months is insane!
To answer the title of your post, I’m just a dev, but I understand it will happen very soon.
Yes, lately OISY is getting tons of upgrades, and it’s one of the products I am really looking forward to. I am a firm believer that for true WEB3, we should get rid of gated browser extensions and mobile apps, and the browser alone should suffice.
I truly hope that once OISY starts gaining traction, we will see existing ICP wallets expanding to browser versions as well.
Don’t get me wrong, you can have a nice user experience with browser extensions and mobile apps, but at the expense of being a hostage to marketplaces that can remove them on a whim.
Is there a roadmap detailing the features planned for the OISY wallet?
Has Dfinity successfully recruited new members for the OISY team?
Github activity
Oisy development falls under digital assets roadmap as far as I can see.
Shifting the Oisy architecture and adding support of the signer standards (ICRC-25 and extensions) seems to be planned for November as of now.
As for a stable release of Oisy, I’m not aware when this is planned at the moment. But once the signer standards are implemented, it should already be usable with dapps across the IC ecosystem.
Together with @AntonioVentilii-D, we merged the support for signer standards into OISY main
last Thursday.
The library we’ve built, enabling anyone to integrate similar signer capabilities as OISY on the IC, will be open-sourced next week (most probably).
Note that I understand the foundation wants more features than “just” the signer standards to declare it no longer in alpha.
Regarding the library is this for the dapp or a signer? For the dapp there’s also already SignerJS and IdentityKit
Signer.
The repo also contains an opinionated relying party client, primarily developed for OISY to validate the implementation, for testing purposes and to some extension provide another implementation of the spec. The foundation recommends using IdentityKit or SignerJS. At least, that’s what I always convey when I interact with teams interested in communicating with OISY.
Cool stuff. Curious about security assumptions of Oisy. It will be blackholed/DAO governed I assume? AFAIK its a web wallet/hot wallet secured and maintained by canisters.So I would have to trust the canister controller, nodes(subnet) and NNS?
Why do we have to keep adding INDEX when importing tokens??? How can we avoid that??? Makes no sense at alll… no other blockchain needs 2 addresses to import a token…
COME ON DFINITY!
Honestly, the Index makes complete sense to me.
It ensures that OISY fetches both the balance and transaction history in sync, eliminating any chance of data mismatch. Without the Index, OISY wouldn’t be able to display transactions, which, in my opinion, is a drawback for a wallet. It would be like having just a balance with no record of the transactions.
As for other blockchains, I’m not sure, but I would assume that some work around this by crawling and storing indexed data on Web2 servers. With an Index, however, everything comes securely directly from the chain.
That said, this feature request was recently submitted—so you may want to upvote it: https://github.com/dfinity/oisy-wallet/issues/2883
Peter, thanks for the answer but… The thing is… How do I find the index for NON SNS TOKENS?
Its a terrible user experience… Think of the average guy that tries ICP for the first time.
And imagine to make a tax report! Its completely imposible in the IC ecosystem!!!
Indeed, I can imagine that: how would you make your tax report without transactions?
Anyway, no need for a long discussion. Team is aware of the request. Noted. Feel free to upvote the linked feature request if you’d like too.
What im saying is… Why in other ecosystem (eth, sol, etc.) I just need to only know ONE address but on icp I need to ADD TWO ADDRESSES? Don’t you see the difficulty from the UX perspective?
Gonna answer one more time as I mentioned in my previous message, your feedback was noted. Feel free to upvote the linked issue if you wish.
Peter, my answer is not being answered… Why transactions can be tracked on ETH adding just a token address but we need to addresses to track transactions on ICP?
ICHouse - Dfinity ICP & Tokens Explorer only need the ledger ID to get all transactions. don’t know the details, but there should be some references. @peterparker
I don’t understand your question. Is that related to OISY?
I think the discussion is related to Decentralized DAB by NFID Labs
ideally Oisy (or any other dapp) would be able to easily lookup the canister id of the index canister for a specific token ledger.
@gatsby_esp on ICP, each token typically defines its own index canister. if this does not exist, it’s not easily possible to get the transfer history of specific principals. you can read more about that here:
the difference to other blockchains is explained here:
so typically you have two canister ids:
- ledger canister id of the token
- index canister id of the tokens ledger
I think the discussion around simplifying (or automating) the lookup of index canister ids should be continued in the other thread mentioned above.
Yes and no. Most meme tokens, for example, only have a ledger without an Index canister.
Note: I didn’t mean there were no technical solutions or alternatives at all. I was simply answering the original question, which was “why an Index canister is used,” and provided a link to the open issue.
Thanks for the explanations and links.