Chi Bảo --> Hi, how i can get balance by account id in smartcontract near-sdk ?

itsedo --> Maybe you can see here
https://docs.rs/near-sdk/3.1.0/near_sdk/env/fn.account_balance.html

Benji | NEAR --> that’s not possible afaik. You can get the balance of the smart contract itself and the balance of the sender but not the balance of an arbitrary account

AnkushSantra --> Good evening, near team members. I have a startup idea that I would love to discuss with near team. I am new to this server, so apologies if I am asking this question in the wrong place. Can someone please send me an appropriate email address or guide me to some team member who would be able to help me out? Thank You.

Benji | NEAR --> If you’re looking for a member of the NEAR team’s opinion, my best suggestion would be to come to office hours. Thé Dev Rel team holds daily office hours every weekday at 2pm ET in the office hours channel. They will be starting back tomorrow I think as the holiday comes to a close.

AnkushSantra --> Thank You so much for so quick reply, but in India, it equates to 12:30 AM (midnight). Any other way? I have created slides to demonstrate my idea as well. Or else, I have to wake up really late to demonstrate it as well.

Benji | NEAR --> Is it sensitive information? Could you post in the channel? If not, feel free to shoot me a DM.

AnkushSantra --> Yes, kind off. Let me share the presentation with you via DM.

AnkushSantra --> Can you please accept my friend request, since I can’t send you a message without the same? Thank You!

Benji | NEAR --> Looks good! I’d reach out to <@!Josh | NEAR> to see if you can get a grant 🙂

silencebringer69 --> Hi! I am trying to create a subaccount and than deploy contract on it. I am facing issues while deploying contract. Kindly review the code and error shared as images. Kindly guide what am I doing wrong? Any help will be appreciated.

Benji | NEAR --> Hey so you should do something like this:

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"); 
        await account.createAccount(
            "in-memory-testing.benjiman.testnet", // new account name
            pubKey, // public key for new account
            parseNearAmount("1") // initial balance for new account in yoctoNEAR
        );

Benji | NEAR --> Basically what’s happening is you’re not properly creating the account and then you try to deploy the contract to the account that wasn’t actually created and it’s yelling at you saying you don’t have the keys to that account.

Benji | NEAR --> In my code snippet, I’m first logging into my account “benjiman.testnet” by setting the private key in the keystore. I then connect to near using the config and keystore and then generate a new keypair for my new account that I’m gonna create. I then go ahead and create the subaccount using my original account benjiman.testnet

Benji | NEAR --> here is the transaction: https://explorer.testnet.near.org/transactions/9tzNYeZ4gAynrQRsronFvpUPDsQm4SHGDX3XUmQoxXd5

silencebringer69 --> Thanks for the answer. From where can I get the private key?

Benji | NEAR --> You can read it in from a file or get it from browser local storage (which is not recommended as you need a FAK to create an account)

Benji | NEAR --> your keys will be stored in the ~/.near-credentials folder usually. If you have your account in the wallet but not locally, use the NEAR-CLI command near login to populate a json file in your near credentials folder with your keys.

silencebringer69 --> Do we have to repeat the same exercise while deploying for the client? Meaning the client will have to share his private key after logging in using NEAR cli.

Benji | NEAR --> from the client, you can login using the wallet object

Benji | NEAR --> https://docs.near.org/docs/api/naj-quick-reference#wallet

Benji | NEAR --> instantiate a wallet connection and then login with a button of some sorts. This will create a function call access key and then you can try and create a subaccount. Since this requires a full access key to do, you will be redirected to the NEAR wallet to authorize the transaction.

Benji | NEAR --> I’m not sure how you’ll handle the deployment of the contract since you’ll have a redirect, however.

devansh --> Can anyone help me configure the whitelist in CMv2? Like how do I create custom SPL tokens and use them for presale?

Benji | NEAR --> I would take a look at this repo if I’m understanding your question correctly. We also don’t have a bridge to solana atm afaik so keep that in mind. https://github.com/near-examples/FT

Phayzee --> I have submitted a security report but haven’t got any reply yet.

Benji | NEAR --> I would wait a few days as people are still on holiday.

Phayzee --> Ohh Ok

0x5F3759DF --> Hi new here, will be forking a protocol over. I’m looking over the docs now, if you have any suggestions of what I should read or videos

Benji | NEAR --> I don’t think we have docs that go over something like that unfortunately. I would just familiarize yourself with NEAR and get a solid mental model of how everything works. With that being said, these are some good resources:

• https://medium.com/nearprotocol/thresholded-proof-of-stake-67b74e616a92
• https://medium.com/nearprotocol/nears-simple-nightshade-a-primer-79643340ae92
• https://medium.com/nearprotocol/how-nears-simple-nightshade-works-90f1c8e6e8af
• https://medium.com/nearprotocol/blockchain-sustainability-how-near-uses-sharding-for-a-more-sustainable-future-4e871043cfb6

0x5F3759DF --> It seems a bit similar to avax with the bridge. Is there native USDC token or should I use a bridge usdc token?

0x5F3759DF --> ty!

alias_willsmith --> Reading through https://docs.near.org/docs/tutorials/contracts/nfts/approvals and wondering why not just set the price ON THE NFT CONTRACT itself vs in different market contracts?! Then there is zero chance of it selling for the wrong price as per the example…
Reading further with the introduction of passing the sale_conditions object to the nft contract, which is along the lines of what I just stated with price setting… doesn’t that make the whole edge case “problem” moot? If the market had to pass a sale_condition logic, what difference would it matter if the market was still listed in approved_accounts_ids?
It would panic by default in that case correct…?
Why limit which marketplace could see your NFT at all? As long as it sells under the conditions provided (sale_condition), is the marketplace even relevant?

Benji | NEAR --> This is a design choice that was made to reduce confusion and to encourage interoperability. When in doubt, abstract things is my philosophy. It would make more sense if the selling mechanisms were all the same. If the NFT was listed on an external contract, the way you would need to sell it would be different since cross contract calls would need to be involved. Having conditional logic as to whether or not the NFT originates from your contract or a different one is annoying and clunky. It’s cleaner to have everything market related on a marketplace contract and everything NFT related on your NFT contract. You could, however, do it this way for sure.

nodderne --> Hi guys, i am a non technical founder of a start up considering building on NEAR but would love if one of you guys could spare me a couple minutes of your time over dm’s. I need to specify to my backers exactly what kind of dev talent i need and since this is my first crypto project let alone building on NEAR i am not quite sure of my needs. Would be highly appreciated if one you guys had a minute 🙂

Benji | NEAR --> The Dev Rel team hosts office hours every weekday at 2pm ET. These will start back up tomorrow as the holiday dwindles down. Feel free to come to that if you’d like. They’re hosted in this channel: https://discord.gg/NxkmgADN

nodderne --> oh awesome, i will join in tomorrow !

itsedo --> Hy, how to simulate input of UnorderedSet in test module? Or I do it in a wrong way?

Benji | NEAR --> You can mirror the behaviour from this: https://github.com/near/near-sdk-rs/blob/2d867cb27732fd680c40d18c9ef9a3b89eb4e0f5/examples/non-fungible-token/nft/src/lib.rs#L168 and just modify to fit your use case

itsedo --> Aight thanks dude

itsedo --> Am I the only one having this error when using near deploy?

Benji | NEAR --> did it end up working? no problems on my end

itsedo --> I think it has to do with WSL, still not working tho