Thank you very very much!)
A post was merged into an existing topic: Internet Identity V2
If you just wanted to try it out without authentication, you can now do so with the demo version.
1 Like
will try it out for sure!
1 Like
Hey @ZenVoich,
just came across this tracker thanks to @cryptoschindler. Great sutff! 
I am wondering if there is any reason you are not supporting authenticating via Internet Identity, Personally I would prefer that over Google or Telegram login.
I am also wondering how you are indexing all the ledgers, which ledgers you actually support and how you decide which new ledgers to add?
My biggest wish for this would be that such API would become open-source, so that anybody could run it and contribute. Do you see a possiblity for that in the future?
Do you have any plans to provide a (paid) public API to access the data? (independent of potential Coineo features)
Best
Marco
Hi @marc0olo
- Backend is completely off-chain, so integrating II will require some additional work.
- II is used only among ICP users (not scalable to other blockchains).
- User cannot share wallet addresses with II. For example, with Plug integration I could auto add all user wallets.
BTW: It would be great if NNS gave the user the ability to share all of his addresses and neurons, so that the user could add it all in a few clicks. - Could be spammed using randomly generated identities(w/o II)
I just pull new transactions from ledgers(icrc3 for tokens and get_transactions for ICP)
I manually add all SNS ledgers and any other tokens with high market cap and proper ICRC-3 support(TAGGR for example has non-standard ICRC-3) or if anyone requested a specific token.
No plans to open source.
No plans for now. But I’d like to hear what use cases you’re considering and what data you’d like to access.
1 Like
thanks for the detailed response!
I see, maybe at some point 
ideally we’d have a good example to follow for integrating II quickly in such applications.
hard to judge from my end right now, I generally think a public (and ideally open source) API to track token balances and the tx-history of users would be nice.
I know we have some projects who all built their own API (e.g. nftGeek) and there is also the IC explorer API. but you cannot just simply run it and add whatever token you want.
I would be happy to hear from other people and builders out there if there is demand for that and what data would be valuable.
tagging @yhabib here who might be able to comment 
1 Like
Hi @ZenVoich
Users can use the reporting feature from the menu to generate a CSV file containing all their neuron accounts, eliminating the need to visit each one manually. Does this help?
Sort of. This requires some explanation for the user and overall more steps than the two clicks for automatic import. Also report does not include SNS neurons and wallet subaddresses.
This just reports ICP staking and transaction not SNS tokens and staking
May I ask what do you mean exactly by “non-standard ICRC3”? AFAIK the token is using the ICRC3 standard, the only thing lacking is the index canister.
Reject text: Error from Canister 6qfxa-ryaaa-aaaai-qbhsq-cai: Canister called `ic0.trap` with message: 'failed to decode call arguments: Custom(Fail to decode argument 0 from table1 to vec record { start : nat64; length : nat64 }
Caused by:
Subtyping error: TypeInner :: Nat64)'.
It uses nat64 instead of nat in icrc3_get_blocks. I did not check further, probably there are more divergences.
1 Like
Thanks for clarifying, I brought this up on Taggr to see if any contributor can look into it.
2 Likes
Hi @ZenVoich
Today’s proposal includes a feature that allows users to export SNS neurons. What do you mean by wallet subaddresses?
1 Like
user’s wallet addresses(accounts), not related to neurons.
Hi @ZenVoich
Would a list of all the account ids (ICP, ckTokens, snsTokens, and neuron account IDs) be helpful for your use case?
Hi @yhabib
yes, definitely
Hey ZenVoich. There was a bug that lead to the divergence from the ICRC3 standard and now it’s been resolved. get_transaction has been also added in this release. Let me know if anything else is needed for the integration of the Taggr token.
1 Like
Hey, Cris.
Just checked #0 TAGGR mint transaction, and I see there is a from field with giceo-65cmv-xxo3t-fojaq-i2tto-vrgcy-3dn52-w45hw value, this field is not intended to be in mint tx, and in new ICRC-3 refinement said “MUST NOT contain tx.from” ICRC-3 refinement by bogwar · Pull Request #199 · dfinity/ICRC-1 · GitHub
Also I parsed to address as
b4zsu-yfcmv-xxo3t-fojmb-27ywr-zvygv-o4atw-6qirg-eevmj-u4svw-lwuqn-nywx2-tpm72-ybgu4-3vmjq-wgy3p-ovxhj-5q
but on the taggr website the address is
2oh3y-xd7c2-hgxa2-v3qco-32bce-yqsvr-gtskw-zo2sb-vxc27-kn5t7-lae
1 Like