Good day, we are creating a Vodacom product mini-app, we have created our public and private keys.. We don't see an option to view merchant details. Could you assist us with the process needed to add our public key for our merchant app.
You can send an email to miniprogramsupport#vodacom.co.za to get your public key configured on the VodaPay systems.
Related
The JS SDK authenticates a wallet by way of requestSignIn(), however, this function takes only a single contract id, and I want the frontend app to hit multiple contracts on behalf of the user.
I suppose I could make it such that all transactions go through a single funnel contract, but this isn't really scalable - what if I want a dApp that also hits contracts outside my control?
What's the advice to solve this? I guess I could make the user signin multiple times, but that's pretty awful..
You can add a prefix for each private key being stored which would let you login to as many contracts as you want.
It's just a string prefix used to namespace the user's private key once they "login" (once they add a FunctionCall access key)
https://github.com/Learn-NEAR/starter--near-api-js/blob/ffe12359f94aa8b558824a3f3ec1f4ba82c0e86a/login-advanced.html#L19
Is there anyway I could either update or delete a public metafield in a product, or a process to create and retrieve a private metafield via GraphQL?
Certainly. As long as you own the API key that created the private Metafield, you can easily make changes to it. The mutations to alter private Metafields on resources are published.
From the docs:
Accounts can be atomically and securely transferred between parties as a native transaction on the network.
I know the currently support Actions on the network are:
CreateAccount
DeployContract
FunctionCall
Transfer
Stake
AddKey
DeleteKey
DeleteAccount
source: https://nomicon.io/Runtime/Actions.html
I know from NEAR Shell that the DeleteAccount action takes an account to be deleted (the "sender") and a beneficiary account (the "receiver").
Is this what is meant by "atomically and securely transferred between parties"? Applying the DeleteAccount action?
Or am I missing something?
The idea behind the secure transfer is the ability to replace access keys.
Let's say you have an account alice and you want to transfer this account to me.
I give you a public key (without revealing the private key).
You create a transaction and sign it with your current private key. The transaction has 2 actions: remove your key, add my public key.
Now alice account has my public key, so only I have access to it. And you don't have access to alice anymore because it doesn't have your key, and you don't know my private key.
I'm setting up a new Near account, and I want to use its keys to sign a message in an app I'm building. How can I do this?
I used the wallet.nearprotocol.com page to create an account. Then, I used nearlib to connect to the testnet, and verify the account's balance and public keys.
But I couldn't find a way to add the account into the localStorage key store or otherwise access a method to sign a message. Nor could I find a wallet plugin or extension that would provide me access.
Generally the idea is that you never transfer given private key between 2 devices / security contexts.
So normally instead of getting private key out of wallet you just want to generate new key pair and request wallet to add public key.
https://github.com/nearprotocol/nearlib/blob/master/src.ts/wallet-account.ts provides relatively easy way to do it for webapp.
Note that it limits access to a give contract ID, so if you need unrestricted access you basically just need to omit contractId.
See examples at https://near.dev/ for WalletAccount usage.
I'm not getting recaptcha image correctly..It says invalid domain key. I actually registered recaptcha in google account for localhost. Can I use recaptcha on localhost? Can someone explain to em why I'm getting this error? Are thee keys keyed in correctly, please?
The key from google:
ANd in my joomla backend, I have to key in public and private key:Where I assumed Site key = public key while Secret Key is Private Key.
Can you go to this link and check your domain is there and you have the correct keys? Also, does this error appear on specific actions (e.g. when submitting the feedback form) or does it always happen when you load any page with a captcha on it?
I suggest you to go through this reCAPTCHA FAQs link.. It will help you
And easiest solution is delete it and register new key. You will be after that.
And one more thing is that secret key is private kind of thing. You do not need to provide it here. Walk on safe side.