totalbanjo --> hello, I’m working on a Near marketplace. This is surely a rather silly question, but I’ve looked through the vast dev documentation/examples and I can’t see any examples of simply -> get NFTs listed for sale from API, at least as a starting point. any help please?

Benji | NEAR --> Do you mean through view calls or a REST API?

totalbanjo --> Rest API

Benji | NEAR --> you’re going to need to keep track of that information yourself and create APIs. The way my team does it is we run an indexer to listen for transactions incoming on our contracts and then do a POST to our API to keep track that there’s a sale and then we can just do a GET whenever if we wanna see all the NFTs for sale.

totalbanjo --> Hmm damn, sounds way more complicated than it should be.

So what if I want to list all NFTs on my marketplace, not just those minted through my contract?

Benji | NEAR --> you can do that through view calls if you’d like but if you want it in a REST API, you’re gonna have to do some infrastructure stuff. You can also loop through your NFTs to populate a DB at the end of each day but that won’t always give the most up to date information throughout the day

totalbanjo --> Looks like I need view calls then

totalbanjo --> Is there an example of doing that using view calls?

Benji | NEAR --> https://github.com/near-examples/nft-tutorial/blob/main/market-contract/src/sale_views.rs

Dav --> Hello guys,
i’m working for guildnet, i’m updating Guildnet Wallet based on latest Near-Wallet.

We have :
1 Server for Near-Wallet
1 Server for Near-contract-helper

I’m still facing issue with Recovery

Step to reproduce:
Create a wallet on https://wallet.openshards.io/ with passphrase
Open a new window on another browser to recover the wallet on https://wallet.openshards.io/recover-seed-phrase
Enter the previous passphrase

Uncaught (in promise) Error: Cannot find matching public key
at Wallet.recoverAccountSecretKey (wallet.js:977)
at async Wallet.recoverAccountSeedPhrase (wallet.js:943)
at async _index.Mixpanel.withTracking.setState.recoveringAccount (RecoverAccountSeedPhrase.js:87)
at async Object.withTracking (index.js:16)
at async RecoverAccountSeedPhrase.handleSubmit (RecoverAccountSeedPhrase.js:84)

(I added some debug log)
secretKey:ed25519:53UVQqDDRGfuGq4iuzCRWNpiZPb24fmYS1hCB5XGFdQVjLGaSuP84hnUy83SDTeNKRurgRZP5FEJ9mTPiirgTfoP
publicKey: ed25519:2gfTh4pWywiutHU4eCAmQUVAHbXxpftDzeQcUMFi73Mj
tempKeyStore: InMemoryKeyStore
implicitAccountId: 1904d35754181ad12f561d62f6984c01f6f8fdc3bee68bcbea606c8e2522cfba

DB :
New account in "Accounts"
New line in “RecoveryMethods”

no new line in “AccountByPublicKeys” and “EmailDomainBlacklist”

So information how to find the problem ?

Dav --> Can Dev check my question : https://discord.com/channels/490367152054992913/542945453533036544/927853928656285708
?
Thank you

Benji | NEAR --> I’ve never worked with Guildnet so I won’t be much help, sorry 😦

Dav --> guildnet is just another network like testnet 😉

Dav --> i suppose i need configure something in helper to get the correct information but need Wallet/ Contract Helper expert

Dav --> <@!Daryl | NEAR> is the boss but very busy right now

Benji | NEAR --> I unfortunately won’t be of much help 😦 I’ve gotta hop to another meeting very soon so perhaps <@!Dorian | NEAR> can take the lead on this?

Benji | NEAR --> Yea Daryl is a really busy person 😦

Dav --> Need to find why contract helper dont return data

Dorian | NEAR --> Hey <@!Dav> What is it exactly you need assistance with?

Dorian | NEAR --> It’s definitely weird…

Dav --> I use default configuration.
Wallet Is on a server and helper on another.

Dorian | NEAR --> Ohh I see

Dav --> Staking work, creation account too. But recovery and get validators who have staking dont work.
I will check again tomorrow but there Is no Doc on it…

Dorian | NEAR --> just out of curiosity what resources were you using to create your own wallet? Maybe I can take a look at your reference material?

Dav --> I used near-wallet from git

Dorian | NEAR --> perhaps we can hop into the office hours room and talk through this?

Dav --> maybe tomorrow, more than midnight here ^^

Dorian | NEAR --> Ah ok haha

Dorian | NEAR --> Quick Q tho, why are you using an inMemoryKeyStore vs local storage?

Dorian | NEAR --> I think if I’m correct the wallet uses local storage

Indispensable --> Hello, I am trying to stake my locked tokens and when I choose a validator and stake, I get the following error: Smart contract panicked: panicked at ‘The balance that can be deposited to the staking pool is lower than the extra amount’. Not sure what this means. Can someone please throw some light on this issue? I tried multiple validators but I get the same error.

Benji | NEAR --> You probably don’t have enough balance. See this thread here. https://discord.com/channels/490367152054992913/490367152054992917/761507094092185630

silencebringer69 --> Hi thanks for the solution, we were able to create sub-accounts by using your solution. Since we need the private key in order to generate a keystore. Is there any way to get the private key of sub-account? We can get the credentials of a sub-account if it is created by using the near-cli but, I am looking for a NEAR-JS-API functionality.

Benji | NEAR --> Hmm that’s a good question. I’ll look into it

Benji | NEAR --> Haha I had a major brain fart. You already have the keyPair!

Benji | NEAR --> ```javascript
const keyStore = new keyStores.InMemoryKeyStore();
const ACCOUNT_ID = “benjiman.testnet”; // NEAR account tied to the keyPair
const NETWORK_ID = “testnet”;
keyStore.setKey(NETWORK_ID, ACCOUNT_ID, KeyPair.fromString(“YOUR_PRIVATE_KEY”));

    const config = {
        networkId: "testnet",
        keyStore, // optional if not signing transactions
        nodeUrl: "https://rpc.testnet.near.org",
        walletUrl: "https://wallet.testnet.near.org",
        helperUrl: "https://helper.testnet.near.org",
        explorerUrl: "https://explorer.testnet.near.org",
    };
    const near = await connect(config);
    
    let keyPair = await KeyPair.fromRandom('ed25519'); 
    let pubKey = keyPair.getPublicKey(); 
    console.log('pubKey: ', pubKey);

    const account = await near.account("benjiman.testnet"); 
    const foo = await account.createAccount(
        "benjiman-in-memory-testing3.benjiman.testnet", // new account name
        pubKey, // public key for new account
        parseNearAmount("1") // initial balance for new account in yoctoNEAR
    );

Benji | NEAR --> You create a keyPair using `await KeyPair.fromRandom`

Benji | NEAR --> and then use the public key of that keypair for your newly created account

Benji | NEAR --> so you have the keypair stored in the `keyPair` variable

silencebringer69 --> How can I deploy a contract from this newly created account? Don't I need a keystore to deploy a contract? What the config will look like for newly created subaccount? I am sorry I am not being able to put the puzzle pieces together. 
const near = await connect(config);
const account = await near.account("example-account.testnet");
const response = await account.deployContract(fs.readFileSync('./wasm_files/status_message.wasm'));
console.log(response);

Dorian | NEAR --> hello!

Dorian | NEAR --> You would need a full access key pair to deploy a smart contract to that account if that make sense.

Dorian | NEAR --> and actually i just made an a similar example for this scenario lol

Dorian | NEAR --> https://github.com/near-examples/contract-that-deploys-contracts-rs

silencebringer69 --> You are a life savior bro! Thanks very much, will give it a try 🙂

Dorian | NEAR --> let me know what you think! haha any feedback would be much appreciated

silencebringer69 --> Sure thing!

Benji | NEAR --> <@!silencebringer69> I wrote up the code for you.

Benji | NEAR --> ```javascript
        const keyStore = new keyStores.InMemoryKeyStore();
        const ACCOUNT_ID = "benjiman.testnet";  // NEAR account tied to the keyPair
        const NETWORK_ID = "testnet";
        keyStore.setKey(NETWORK_ID, ACCOUNT_ID, KeyPair.fromString("YOUR_PRIVATE_KEY"));
        

        const config = {
            networkId: "testnet",
            keyStore, // optional if not signing transactions
            nodeUrl: "https://rpc.testnet.near.org",
            walletUrl: "https://wallet.testnet.near.org",
            helperUrl: "https://helper.testnet.near.org",
            explorerUrl: "https://explorer.testnet.near.org",
        };
        const near = await connect(config);
        
        let keyPair = await KeyPair.fromRandom('ed25519'); 
        let pubKey = keyPair.getPublicKey(); 
        const subAccountId = "benjiman-in-memory-testing-contract.benjiman.testnet";
        const account = await near.account("benjiman.testnet"); 
        await account.createAccount(
            subAccountId, // new account name
            pubKey, // public key for new account
            parseNearAmount("1") // initial balance for new account in yoctoNEAR
        );
        keyStore.setKey(NETWORK_ID, subAccountId, keyPair);
        console.log('keyStore: ', keyStore)
        
        const subAccount = await near.account(subAccountId); 
        const response = await subAccount.deployContract("./main.wasm");
        console.log('response: ', response)

Benji | NEAR --> This will create a sub account and then deploy a contract to it

Benji | NEAR --> See here: https://explorer.testnet.near.org/accounts/benjiman-in-memory-testing-contract.benjiman.testnet

Benji | NEAR -->

Benji | NEAR --> just set the key in the keyStore using the keyPair object

silencebringer69 --> That worked, thanks! You are awesome 👍

AnkushSantra --> <@!Benji | NEAR> Good Evening, Sir. Can I expect the Dev Rel team to be online today in the office hours?

Benji | NEAR --> Indeed we shall 🙂 - 2pm ET

AnkushSantra --> Thank You for the quick reply. I would surely join today.

demipop --> hey sorry for simple Q’s. if there’s a channel for folks working on indexer/queries happy to chat in there. i usually assume i’m missing something haha:

has anyone figured out a good way to rpc query to get lockup accounts for account_ids?

vmod --> how fast are view methods in a single contract usually

imz13 --> hi… did i lose my funds if i sent NEAR to the token address i was provided by near wallet instead of to my user ID?

Dorian | NEAR --> Like the one you used to initiate your account?

Benji | NEAR --> <@!imz13> <@!BT1> can you ask in <#🤝 │ community-support>

imz13 --> There’s a recovery method

imz13 --> Thank goodness

Aaron | Vital Point AI --> Anyone know what the equivalent of the RUST json_types -Base64VecU8 is for AssemblyScript?

Hatchet --> Anyone know why the NFT standard implementation only refunds amounts greater than 1 yoctoNEAR? https://github.com/near/near-sdk-rs/blob/master/near-contract-standards/src/non_fungible_token/utils.rs#L39

Benji | NEAR --> how are you gonna refund 0 yoctoNEAR? You can’t refund nothing

Benji | NEAR --> oh you’re asking if it’s 1 yocto NEAR?

Hatchet --> But it won’t refund 1 yoctoNEAR

Hatchet --> yes exactly

Benji | NEAR --> yea I mean that’s an edge case and that’s such an insanely small unfathomable number that it doesn’t matter

Benji | NEAR --> it could be greater than or equal to

Hatchet --> It just seems like a weird and unnecessary exception - why not just say if refund > 0?

Benji | NEAR --> you could do that for sure

Hatchet --> Ok, just confirming it’s not there for some other reason. Thanks!

Benji | NEAR --> haha yea no problem !