SOLMONGER --> is there anything similar to metaplexes candy machine on solana on near yet?

James | NEAR --> https://docs.near.org/docs/tutorials/contracts/nfts/minting-nfts

SOLMONGER --> ooooooh interesting thank you so much! just bridged over a couple hours ago

hoangtrinhj --> Hi,
Can you share the repo that you guys are working on? (Hardhat similar tool for Near)

uditgulati00 --> We’ll be starting the work this month.

uditgulati00 --> Hi <@!Benji | NEAR>, I’ve made a draft for grant proposal. Where shall I send it? Thanks.

Benji | NEAR --> If you wanna apply for a fast grant, DM <@!Josh | NEAR>. If you wanna go through and apply for a large grant, apply here: https://near.org/grants/

uditgulati00 --> I DMed Josh but didn’t get a response. Btw, what’s the difference between fast grant and the other one?

Benji | NEAR --> fast grant is <20k going through near.org/grants is >20k

Thomas997TT --> Could someone help me out I have some questions about the NEAR mainnet explorer:
-How are the charts and stats calculated?
-For example, how is daily active number of contracts defined?

Benji | NEAR --> I’m not too sure <@!khorolets> do you know?

mhassanist --> Hi everyone
I’m trying to call a contract and I’m getting this error

Scheduling a call: dev-1641547122393-62907146028495.getGreeting({accountId: mhassanist.testnet})
An error occured
SyntaxError: Unexpected token a in JSON at position 1
at JSON.parse ()
at scheduleFunctionCall (C:\Users\MSaudi\AppData\Roaming\npm\node_modules\near-cli\commands\call.js:54:84)
at async Object.handler (C:\Users\MSaudi\AppData\Roaming\npm\node_modules\near-cli\utils\exit-on-error.js:52:9)
SyntaxError: Unexpected token a in JSON at position 1
at JSON.parse ()
at scheduleFunctionCall (C:\Users\MSaudi\AppData\Roaming\npm\node_modules\near-cli\commands\call.js:54:84)
at async Object.handler (C:\Users\MSaudi\AppData\Roaming\npm\node_modules\near-cli\utils\exit-on-error.js:52:9)

It is the default project contract

I’m calling it like that
near call dev-1641547122393-62907146028495 getGreeting ‘{“accountId”: “mhassanist.testnet”}’ --account-id=mhassanist.testnet

mhassanist --> I got it fixed. It was the escape character issue in windows "

Benji | NEAR --> works for me:

Benji | NEAR -->

bailey12 --> hi, this is the stackoverflow question regarding on the problem of not able to delete wallet with too many states.

https://stackoverflow.com/questions/70616916/delete-near-wallet-error-because-account-has-too-many-state

Any help is much appreciated. Thank you

Benji | NEAR --> I would just loop through and delete all your keys in a script

bailey12 --> can you walk me through the steps on stackoverflow when you got times? I am really appreciate it

poddubny --> hey guys! sometimes explorer doesn’t show all transactions related to specific contract. E.g. in contract https://explorer.testnet.near.org/accounts/swt07.intmainreturn000.testnet there is no tx https://explorer.testnet.near.org/transactions/Hb1h74bQGhTG1LGwxA7okhKfdjyGVvS9WAd1boreePEC (however, this tx was successfully processed by contract)

Benji | NEAR --> cc <@!khorolets> I have no clue… It should but the user is right and I can’t find the hash on the account’s transaction list

CaptainB --> hello! easiest way to launch a nft collection on your network?

Benji | NEAR --> https://docs.near.org/docs/tutorials/contracts/nfts/introduction

CaptainB --> thanks! any proper examples/github code for creating a big collection?

CaptainB --> on solana we had metaplex candymachines, nothing similar here?

illus --> Is there any way I can get other return types than Promise through cross-contract-call?

Benji | NEAR --> I’m a solid 80% sure that you can only use promises. <@!austinabell> can u give a more definitive answer haha. In docs, it says NEAR introduced promises to make dev’s lives easier but does that mean promises are the only way to deal with cross-contract calls?

illus --> It’s too complex even get result of other contract’s getter function…

austinabell --> Do you mean like the return type from the function you are calling? If so, you can’t and the reason is because that function call is not done within the current execution and is happening later (usually next block) so you can’t use a value that may or may not succeed in the future.

Generally the pattern for following up with this data is with callbacks, which essentially uses this data from this future computation and continues to execute with the resolved value you want. Unfortunately breaking up the logic into pieces like this is the only way to handle this asynchronous execution, but hopefully in the future we can abstract over this 🙂

See some docs on callbacks here: https://www.near-sdk.io/cross-contract/callbacks

Evan Feenstra --> how can you use near-sdk-js not in a browser? new WalletConnection in node.js gives “window is not defined”

vmod --> you cant use wallet connection in node

vmod --> you need to use InMemoryKeyStore

vmod --> and you do KeyPair.fromString(“private key”)

vmod --> and set key to that

vmod --> because wallet connection is defined only on the frontend to keep security of user wallet

Evan Feenstra --> got it

joaquimley --> Take a look at NEAR 101, it might help you to get a grasp of some of these small details:

• https://docs.google.com/presentation/d/1jNpzqRAm44HGefgrlOpXV-qwJQQ1X8JOBSpxhkUNchI/edit#slide=id.g7ff97e764c_0_349

trevoro --> is anyone working on the near hackathon at dev.post? I am seeking some team members.

lev_s --> Hello hello, I was wondering what the proper way to burn fungible tokens are?

Benji | NEAR --> just remove them from state 🙂

lev_s --> Ok sure. There is this line in the rust ft contract: https://github.com/near-examples/FT/blob/e2161c8215b2589335245992ff3ce62fdc8d32da/ft/src/lib.rs#L82. I was wondering from where that gets called?

chandanvishwakarma2 --> How can I make multiple copies of an NFT and put it on marketplace…it there any source code or example ?

Benji | NEAR --> u can mint multiple NFTs then just put them all on the marketplace if that’s what ur looking for or do you want something more complicated? I’d highly recommend checking out this tutorial series btw: https://docs.near.org/docs/tutorials/contracts/nfts/introduction