Mouradif --> oh no I missed the office hours ><

Mouradif --> I wanted some help to setup my local node, is someone still available for that?

Mouradif --> regarding these issues I had

Dorian | NEAR --> Your own local node for development testing?

Mouradif --> yes

Dorian | NEAR --> Ah perhaps near workspaces could be of use to you

Dorian | NEAR --> https://github.com/near/workspaces-rs

Dorian | NEAR --> https://github.com/near/workspaces-js

Mouradif --> I’ll explain the issue I have:

2 weeks ago, I was working on my hackathon submission for METABUILD (a decentralized dns registrar), I had my localnet installed (compiled nearcore then spun up the node with nearup run localnet --binary-path /path/to/compiled/nearcore), it ran 4 nodes and I could create accounts that ended with .node0 , .node1, …

I created the account dns.node0 and deployed my smart contract on it, then I could query it to make sure everything worked.

2 weeks later, I come back and try to resume working on it, I get the error that says The node does not track the shard ID 0. I clear up my whole setup, restart a new node from scratch following exactly the same steps (except I was one version higher I imagine) and now I can’t create accounts anymore

Dorian | NEAR --> Let me look into this a bit more for you

Dorian | NEAR --> which version of nearcore are you using?

Mouradif --> I compiled the master branch

Mouradif --> this commit: 30dcab97baec823a0f4be8ac77132f00ebd2b7e3

Mouradif -->

Mouradif --> ```
$ ./neard --version
neard (release trunk) (build crates-0.11.0-52-g30dcab97b) (protocol 50) (db 31)

Dorian | NEAR --> what did you do to produce this error? 

Are you able to reproduce it?

Does the error come back when you are trying to query your node?

Mouradif --> Which error? You mean `The node does not track the shard ID 0` ?

Dorian | NEAR --> yeah

Mouradif --> whenever I do `near call` with anything that ends with `.node0`

Mouradif --> wait sorry

Mouradif --> I'm redoing everything and now I was able to create an account

Dorian | NEAR --> 😮

Mouradif --> but I get another error with `near call`

Dorian | NEAR --> There is an existing issue on this and I'm wondering if this same issue is happening to you. But the issue is pretty old, so I'm not 100% sure so I'm going to ask one of our engineers

Dorian | NEAR --> https://github.com/near/nearcore/issues/4340

Dorian | NEAR --> what's the error your getting here?

Mouradif --> `Can not sign transactions for account dns.node0 on network localnet, no matching key pair found in InMemorySigner(MergeKeyStore`

Mouradif --> same when I pass `--keyPath` and provide a path to the key

Mouradif --> ok sorry again

Mouradif --> I re-created the account `dns.node0` and it worked

Mouradif --> I probably had the old key from the previous setup

Mouradif --> I feel so silly 😄

Mouradif --> Thanks for your help <@!Dorian | NEAR> and sorry for wasting your time

Dorian | NEAR --> wait what lol

Dorian | NEAR --> it just started working?

Dorian | NEAR --> I mean I'm glad but I'm curious to know why your original account stopped working haha

MelkeyDev --> <@!bucanero> I want to launch my NFT collection on NEAR. I have the images generated and I have the contract written in solidity, then I think I need to re write in Rust. Do yo have any resources on how I can do this seemlessly?

bucanero --> Yes, in that case you’ll have to re-write your contract in Rust, so it can run on NEAR. We recently published a complete NFT smart contract tutorial series: https://docs.near.org/docs/tutorials/contracts/nfts/introduction

bucanero --> It covers everything and follows the NFT standard, so I think it should provide you a clear path to follow in your contract’s migration.

MelkeyDev --> Okay cool. It looks pretty straight forward

MelkeyDev --> <@!bucanero> I got a question though

MelkeyDev --> Rn, all my images and MD are on IPFS. Does Near require the meta data to be in a specific formatin or some thing ?

bucanero --> The NFT standard on Near has some requirements for metadata:
https://docs.near.org/docs/tutorials/contracts/nfts/skeleton#metadatars

bucanero --> but the content and media files can be on IPFS, that’s totally ok 🙂 (and actually encouraged so you don’t waste money on Near storage)

MelkeyDev --> Kk, I am going to look into it this week

MelkeyDev --> Ill post here if I get stuck or have any questions,

MelkeyDev --> thanks mate

anilk --> Hello

anilk --> What makes a contract method GET so that there is no transaction cost

joaquimley --> In simple words, if there is no mutation of state/data, you are only fetching and reading the state.

A good rule of thumb is if your method’s first argument only takes a reference &sef is a view method, if you need a mutable reference &mut self most likely you are dealing with a call method

restockflippaz --> how to get private key

Peter Priew Sommon --> Help me I cannot connect to Paras

Peter Priew Sommon --> I try many times

Peter Priew Sommon --> Not complete

Peter Priew Sommon --> I use Ledger Nano X on FireFox

Epiro --> Is there a way to make a struct returnable as JSON in a contract method in the near sdk i.e

pub struct RespObj {
    text: String,
    account: String,
}
...
#[near_bindgen]
impl Contract {
    pub fn get_resp(&self) -> RespObj {
        RespObj {
            account: String::from("an_account"),
            text: String::from("this is text"),
        }
    }
}

I’m new to rust so perhaps I just need some pointers on how to read / act on this error message:

error[E0277]: the trait bound `RespObj: Serialize` is not satisfied
    --> src/lib.rs:30:1
     |
30   | #[near_bindgen]
     | ^^^^^^^^^^^^^^^ the trait `Serialize` is not implemented for `RespObj`

Epiro --> Fixed it by adding some macros to the struct definition: ```#[derive(Serialize, Deserialize, BorshDeserialize, BorshSerialize)]
#[serde(crate = “near_sdk::serde”)]
pub struct RespObj {
text: String,
account: String,
}

Reading though this was helpful: https://github.com/near/near-sdk-rs/blob/master/HELP.md

illus --> If cross-contract call panicked inside, calling tx would revert at all like solidity?

illus --> or should I handle the error using callback?

0x5F3759DF --> This but for NEAR?
https://etherscan.io/proxyContractChecker

0x5F3759DF --> How do I verify a contract as a proxy contract?

MelkeyDev --> Hey everyone

MelkeyDev --> Glad to be here

MelkeyDev --> I have a question, does anyone have any good resources (besides the docs) on how to launch an NFT collection on the NEAR protocol ? I am reading the docs and I am just a little confused

MelkeyDev --> I am looking at how to get already generated pngs and metadata.json onto the Near protocll

bucanero --> do you want to build your own NFT smart contract, or you just want to launch an NFT collection? if you don’t want to build your own contract, you might want to check https://satori.art/ and https://www.mintbase.io/

fcl --> does near have a custom parser/runtime for wasm?

fcl --> or just using a library?

Zap --> hey, im trying to drop a collection on NEAR im trying to find out how i cna make a mint website like is there a ‘candy machine’ on NEAR

geeta_rao_agrawal --> Hi I was following this link https://docs.near.org/docs/tutorials/near-indexer but getting below error error: failed to select a version for the requirement near-rust-allocator-proxy = "^0.2.8"
candidate versions found which didn’t match: 0.3.1
location searched: crates.io index
required by package neard v1.2.0 (https://github.com/nearprotocol/nearcore?rev=a668e4399655af513b0d90e0be694dad2448e6cd#a668e439)
… which is depended on by near-indexer v0.9.1 (https://github.com/nearprotocol/nearcore?rev=a668e4399655af513b0d90e0be694dad2448e6cd#a668e439)
… which is depended on by example-indexer v0.2.1 (C:\Users\mgeet\example-indexer)

Jennie --> Hello 👋
Please can someone point me to the faucet URL for NEAR?

bucanero --> if you need testnet tokens, keep in mind that when you create a testnet account you’ll get testnet tokens

Jennie --> okay, thank you. So, just to clarify, without creating an account, I cannot get tokens?

bucanero --> Not currently; so the easiest way to get testnet tokens is to create a testnet account. 🙂

Jennie --> ohh! Thank you, Damian.

bucanero --> You’re welcome. Btw, if your dev project needs a big amount of testnet tokens, let us know and we’ll try to help you out. 🙂

Jack Robson --> Why does this return an error? Error: Querying [object Object] failed: wasm execution failed with error: FunctionCallError(MethodResolveError(MethodNotFound)). from code:

    account, // the account object that is connecting
    "example-nft.testnet",
    {
        // name of contract you're connecting to
        viewMethods: ["nftTokensForOwner"], // view methods do not change state but usually return a value
        changeMethods: [], // change methods modify state
    }
);

const response = await contract.nft_tokens_for_owner();
console.log(response);```

Jack Robson --> If it helps, I'm trying to turn this following line of code into a SDK handled function:
`near view example-nft.testnet nft_tokens_for_owner '{"account_id": "'$NEARID'"}'`

Dorian | NEAR --> hello

Jack Robson --> I need to pass the args JSON -_-''

Jack Robson --> Hi 🙂

Dorian | NEAR --> oh did you figure it out?

Jack Robson --> Yes 🙂

Dorian | NEAR --> haha great!

Jack Robson --> Still a little juice left in the brain today it seems 🙂

Jack Robson --> Nearly finished for the day, just final bug to crush, can anybody help? I’m trying to mint an NFT but I’m getting vError: {"index":0,"kind":{"ExecutionError":"Smart contract panicked: Must attach 7730000000000000000000 yoctoNEAR to cover storage"}}

Jack Robson --> const response = await contract.nft_mint({ "token_id": "token-1", "token_metadata": { "title": "My Non Fungible Team Token", "description": "The Team Most Certainly Goes :)", "media": "https://bafybeiftczwrtyr3k7a2k4vutd3amkwsmaqyhrdzlhvpt33dyjivufqusq.ipfs.dweb.link/goteam-gif.gif" }, "receiver_id": this.subAccountName, "accountId" : "jackrobsonalpha.testnet", "amount" : 0.1 });

Jack Robson --> —

Jack Robson --> answer is:

          {
            "token_id": "token-1",
            "token_metadata": {
                "title": "My Non Fungible Team Token",
                "description": "The Team Most Certainly Goes :)",
                "media": "https://bafybeiftczwrtyr3k7a2k4vutd3amkwsmaqyhrdzlhvpt33dyjivufqusq.ipfs.dweb.link/goteam-gif.gif"
            },
            "receiver_id": this.subAccountName,
            "accountId" : "jackrobsonalpha.testnet",
          }, 
          "300000000000000", // attached GAS (optional)
          "7730000000000000000000", // attached GAS (optional)
        );

Dorian | NEAR --> <@!Jack Robson> Did you get both your Qs answered?

Jack Robson --> First day, can’t figure this one out…
throw new providers_1.TypedError(Can not sign transactions for account ${this.accountId} on network ${this.connection.networkId}, no matching key pair found in ${this.connection.signer}., 'KeyNotFound');

Probably an easy error but not sure what I’m missing:
https://gist.github.com/jackrobsonalpha/b719cd86f1d5ecd31e68f3e2298f7c5f

Jack Robson --> It’s probably related to his bit:

        "token_id": "token-1",
        "metadata": {
            "title": "My Non Fungible Team Token",
            "description": "The Team Most Certainly Goes :)",
            "media": "https://bafybeiftczwrtyr3k7a2k4vutd3amkwsmaqyhrdzlhvpt33dyjivufqusq.ipfs.dweb.link/goteam-gif.gif"
        },
        "receiver_id": "discord-example.testnet",
        "accountId" : "discord-example.testnet", // not sure if passing this right 
        "amount" : 0.1 // or this?
    });```

Jack Robson --> hm…getting this error out of nowhere Property 'keyStores' does not exist on type 'typeof import("/Users/ph/Projects/juno/moneta/tests/cucumber-with-typescript/node_modules/near-api-js/lib/index")'.

Radkin --> <@!Jack Robson>, I cannot answer however, I point out that I do not see a way for the online wallet to create the keystore. It appears to store the pvt key in plan text. Of course you can use a Near library or your own code to create it from the seed, but what a drag. All great wallets allow for a keystore or password alone to encrypt/decrypt your seed! It is ture that storing even an encrypted seed may be risky, but what is the alternative? Storing a plaintext seed/key is far worse. SO, Near devs, please tell us how youallow for sends with a new wallet with no 2FA. Where and how do you store the pvt key?

Jack Robson --> I’m not sure, it’s my first day, still getting to grips with this

Jack Robson --> adding this above the import line fixes it // @ts-ignore

Jack Robson --> I managed to figure out my earlier questions, though you might be able to help with my current head scratcher:
contract.methodName(args, gas, amount) deprecated use contract.methodName({ args, gas?, amount?, callbackUrl?, meta? })
Not sure what values to put for callbackUrl and meta to get this to disappear.

Aaron | Vital Point AI --> In reference to the 30% of transaction fees that go to the contract(s) involved - I haven’t been able to find anything indicating if there was a way to have that directed to a specific account when the transaction occurs. Is it up to the developer to build something into the contract to extract it. If that’s the case, is there best practice for doing so? Not building some kind of withdrawl function in might mean those funds become inaccessible, but seeing a withdraw function in a contract (locked or not) might cause some questions/concern. Wondering how others are dealing with this?

Josh | NEAR --> Not sure if I’ve seen an example of this, but we should certainly have this documented somewhere. Let me either find an example or create one for you 🙂

visiere --> hi guys, I have a little question about how to read these data pulling queries. How are daily_receipts_per_contract different from ingoing and outgoing txns? Is it the sum of ingoing and outgoing for a unique address? If we sum ingoing and outgoing transactions, does that give us a total number of transactions? And lastly, is it possible to track individual projects by address?

bayowulf --> Hello sers. I’m taking data from NEAR Explorer and NEAR’s mainnet analytics. If you can help me just a few basic questions, that would be awesome!

1. What are the differences between ingoing and outgoing transactions? ingoing + outgoing txs = total number of tx, right?

2)How are daily_receipts_per_contract different from ingoing and outgoing txns?

3)How do accounts relate to deployed contracts? How can we verify which accounts belong to which projects?

I’m trying to understand how many txs and how much gas usage comes from each project. I want to create a database for NEAR.

bayowulf --> Sorry to tag you ser, any chance you know about these things? <@!Benji | NEAR>

bayowulf --> <@!Dorian | NEAR> My question is probably very easy to answer for you, so I would really appreciate it if you can take a look at it, especially the 1st and 2nd ones. Thanks a lot 🙏

Dorian | NEAR --> 1) What are the differences between ingoing and outgoing transactions? ingoing + outgoing txs = total number of tx, right?
outgoing ( are tx sent out by the account, like if I’m using my account example.near to call a method on the contract on contract.near that’s one transaction)

ingoing (Calls being made on my account that has a contract deployed onto it)

2)How are daily_receipts_per_contract different from ingoing and outgoing txns?
( each transaction has a receipt to it, I’m not finding where you are seeing this but I’m guessing just the total transactions made that day)

3)How do accounts relate to deployed contracts? How can we verify which accounts belong to which projects?
(every account is technically a smart contract. Each account starts off as a smart contract with no code on it. When you deploy a contract you are deploying code in the form of a .wasm file onto that account. So now that account is a smart contract with code on it. Data and information tied to that account are stored in that account’s state on chain.

There are a few ways you can find out what account is deployed to what project. you can use the explorer to see which account your transactions have been called on. If the project is open source they may have the account name in their code somewhere unless it’s saved as an environment variable. probably my default way would be to check the explorer

bayowulf --> Thanks for the detailed answer! These are awesome!!!

Jack Robson --> side question, are you folks using Typescript in your projects?

i’m only new but I keep running into weird errors and having to add @ts-ignore in different places, wondering if I should have just started with JS

lerd.dev --> Hi
I am trying to implement Near login with backend,
I am looking at exiting JS implementation
and I am not quite sure what is the idea behind public_key and all_keys params in callback url
Anyone can help me with that?

Dorian | NEAR --> what are you looking at as your reference?

josedlujan --> I have an specific problem with this , the function to getAccountBalance()
https://stackoverflow.com/questions/70677582/function-getaccountbalance-doesnt-work

Dorian | NEAR --> hello

Dorian | NEAR --> A few Q’s with this one, how did you initialize your account object? being the first one

And may i see your reference material?

josedlujan --> I add the code in stackoverflow <@!Dorian | NEAR>

josedlujan --> About this someone have an idea…i think is a issue with the configuration

kerga --> Hello, are you going to add the possibility of coding in ruby ​​on rails on the Near blockchain?

Dorian | NEAR --> I haven’t heard of anything specifically related to that but I can ask around.

kerga --> Thanks I’m curious to know. I know there is a gem for ethereum

kerga --> Today with Ruby on Rails7 it is very simple and fast to deploy a fullstack application. It can be a good thing for the development of Near

Evan Feenstra --> You can use near-api-js in a Ruby app frontend. Near dapps (and all dapps) are all about giving control to the users, meaning interacting directly with the blockchain from the client (javascript). If you are holding user keys in the backend than there is no reason to use a blockchain hehe

kerga --> Amazing, I look at this