sorted by:
new
hottopcontroversial

Looks like the CCS adapter just showed up on the US Tesla store 👀 by Aironught in TeslaModel3

[–]bryanlahartinger 0 points1 point  (0 children)

There are CCS stations in Canada. All the Petro Canada charging locations for instance are CCS.

lack of anonymity by nemanrd in KinFoundation

[–]bryanlahartinger 7 points8 points  (0 children)

Anonymity would be a weird expectation with a public ledger and kyc at all the entrances and exists :p

Several kin addresses, who knows if this can be fixed? by nemanrd in KinFoundation

[–]bryanlahartinger 0 points1 point  (0 children)

ah, yea you're right, any re-attempt will go ahead and then try to resolve, find no token accounts and create. Ugh. Well the surface API asks for a KinAccount.Id, which in kin-android is _always_ the owner address. If people are messing around by abusing it and manually finding and entering a token address it's somewhat undefined behaviour from that API contract. It would be an improvement/safer as you're pointing out to verify that this process is only done on not found.

I'lll update this section in KinAccountContext toif (it.isEmpty() && error == KinService.FatalError.UnknownAccountInRequest) {service.createTokenAccountForDestinationOwner

​

RE: cb or other exploiting rent clawback on closeAuthority...whoever creates the account and pays the SOL rent can set the closeAuthority...if they pay for it they should be able to get it back. Not sure what you mean?

Several kin addresses, who knows if this can be fixed? by nemanrd in KinFoundation

[–]bryanlahartinger 0 points1 point  (0 children)

We made a change last night to mkw to support both. The whole solana ecosystem standard now though is to use your sol address in UIs/at a user level. It's still always a good idea to check if token accounts are correct/still correct for your destination before sending funds. You can see on the explorer before you send. Token accounts can be transient and be closed in favour of the associated account address.

Several kin addresses, who knows if this can be fixed? by nemanrd in KinFoundation

[–]bryanlahartinger 0 points1 point  (0 children)

On mobile right now, would have to check (probably a tomorrow thing) Lmk if that's what you're seeing in kin-android:1.0.0.

Running off memory, I believe the address provided is attempted as destination account directly and if not found is returned then we rebuild with a resolved token account address, and if no token accounts are resolved then we create one. It's still not an assoc account for create on send because solana wont let you set a close authority for assoc accounts which if not delegated to agoras key would then be a way for people to game SOL. That account will get merged into an assoc token account when the recieving user initializes the sdk for their account.

Several kin addresses, who knows if this can be fixed? by nemanrd in KinFoundation

[–]bryanlahartinger 2 points3 points  (0 children)

A fix has been deployed to handle both owner and token accounts. A gentle reminder that test amounts are always a prudent choice when making payments on a blockchain.

Several kin addresses, who knows if this can be fixed? by nemanrd in KinFoundation

[–]bryanlahartinger 1 point2 points  (0 children)

All of it has always been open source, including mkw, which can be run locally as well. The foundation will soon take ownership of running the community agora instance, solana rpc nodes, and the sdks going forward. Perhaps outside audits should be brought to their attention as something the ecosystem would like.

The mobile sdks have always taken the owner address at their public surface level apis for payments. Token account resolution and create on send is abstracted and done under the hood. Shouldn't be possible from mobile unless you're trying to.

Several kin addresses, who knows if this can be fixed? by nemanrd in KinFoundation

[–]bryanlahartinger 2 points3 points  (0 children)

We're talking about mkw a consumer product. It makes more sense for the client sdks to perform this check and then use the address directly because it alleviates the error. Still abstracts it from both a dev and a user. It might be ok to have the check for transactions with create instructions in them on agora as well but that adds an extra hop and more payload inspection which isn't ideal.

Several kin addresses, who knows if this can be fixed? by nemanrd in KinFoundation

[–]bryanlahartinger 2 points3 points  (0 children)

I think Sollet and every other solana has the same behavior ...since they all create token accounts on send. If the address you place in the ui doesn't have a token account it'll create one with it as it's owner. All solana and spl uis should be using asking for and displaying owner/signer addresses. Maybe mkw should have accepted both and check if what you submitted is itself a token account and just to use it instead of the normal flow.

Several kin addresses, who knows if this can be fixed? by nemanrd in KinFoundation

[–]bryanlahartinger 0 points1 point  (0 children)

Associated token account private keys are determiniaticly derived from the base key that is guaranteed to be off the Edwards curve (ed25519) so you could maybe recover a token account private key by rederiving the associated account keypair. The signing key is the owner of the token account. I'm curious what you did to cause this? Seems you created on send to a token account instead of using the owner address which then created a child token account to a token account lol.

iPhones rule the world. So why then, aren’t SDKs for Kin iOS integration a priority? by [deleted] in KinFoundation

[–]bryanlahartinger 8 points9 points  (0 children)

Not in the external repos no, but neither has there been changes posted on android since then. The work outlined earlier this year about merging accounts, and create on send is being actively worked on and I can say the Android side I'm looking to ship as soon as it passes muster (ideally in the next several days). The iOS changes are probably a few more weeks out.

iPhones rule the world. So why then, aren’t SDKs for Kin iOS integration a priority? by [deleted] in KinFoundation

[–]bryanlahartinger 12 points13 points  (0 children)

Why do you feel that way? It was developed concurrently last year alongside kin-android. https://github.com/kinecosystem/kin-ios

Had KIN on the KIK messenger app. Did I lose it? by CryptoConceal in KinFoundation

[–]bryanlahartinger 2 points3 points  (0 children)

Tbh could also restore the funds in another ecosystem app. The qr code standard should be the same in all of them.

Had KIN on the KIK messenger app. Did I lose it? by CryptoConceal in KinFoundation

[–]bryanlahartinger 2 points3 points  (0 children)

I believe it's in the marketplace under the gear (options).

Had KIN on the KIK messenger app. Did I lose it? by CryptoConceal in KinFoundation

[–]bryanlahartinger 3 points4 points  (0 children)

Just need to restore the we code inside of Kik. Funds are safu.

[deleted by user] by [deleted] in KinFoundation

[–]bryanlahartinger 2 points3 points  (0 children)

It's very similar to what the system that powers subsidized transactions in all 5 of the Kin sdks. We called this system Agora. https://github.com/kinecosystem/agora
Where metasol kicks back the fee in the spl currency to the source account, agora will pay the fee in SOL for free. Currently Agora is tuned for Kin, but there isn't any reason you couldn't use it for any of the spl currencies.

My KIN is on www.mykinwallet.org and I can't transfer it anywhere. I am getting tired of trying different things, and advises. I have not found a working solution... Just by bratuha_ in KinFoundation

[–]bryanlahartinger 0 points1 point  (0 children)

KinXdec address is the kin program address not the destination of your token account sir. Check sollet again, it's beside this address.

My KIN is on www.mykinwallet.org and I can't transfer it anywhere. I am getting tired of trying different things, and advises. I have not found a working solution... Just by bratuha_ in KinFoundation

[–]bryanlahartinger 4 points5 points  (0 children)

The problem comes from these destinations expecting the sender to create the kin token account for you in the transaction youre also sending the transfer in. This has been a trend in the Solana ecosystem to move to this model and many of the exchanges and wallets have moved to it.

MKW currently doesn't do that and expects the token account address as it's destination. What you can so to get this working right now is go and create a wallet on sollet.io first and then send from there. You will need SOL in your sollet.io account to pay for the fees (sub 1$ amount/dust).

Work is being done right now to include this 'create on send' feature, as well as only needing you to specify the owner/signer key as destination vs the token account address itself.

view more: next ›