Tried it in Ubuntu terminal and:
``{āerrorā: āunauthorizedā}
you can also try with chain id ā0x539ā instead of ā1337ā
Ok, trying with itā¦ was unauthorized on the devchain reset 
Did not work, I am restarting the server. Feel we are getting close, I am going to cry when we make it
try to double check if the contract has the expected address
Yes it is the one, saw it in the console.log and in the hardhat node I can see the 3 transactions, creating the NFT, approving and listing it to the Marketplace (with the expected contract: 0x5fbdb2315678afecb367f032d93f642f64180aa3)ā¦ and that node is being watched by the Cloudā¦
Hi @cryptokid , I have been struggling for a while and I have not been able to solve it. Do you know what else could be failing? Thank you a lot for your helpā¦
I donāt know what it is now, it doesnāt find the events with that topic and address
it does sync new blocks, it is on block 50 now
you could try to add an address to sync to see if it works as expected
Ok, I will try. Where are you seeing that? I would like to know or use the tool to test and see until I get itā¦ thanks a lot again
I am connecting directly to the server, you can not do that
try to add to watched addresses that contract address 0x5fbdb2315678afecb367f032d93f642f64180aa3 in admin interface
No, added the event from the interface and same thingā¦
I mean to add a watch address, not an event sync from the interface
@cryptokid I do not know what happened, close VS opened again, started anything back again and now the database uploaded after hearing the event! It does not have anything to do with hearing the contract, right? I think it was the nonce of the node, because I were never able to reset the local devchain, do you think so?
it shouldnāt be related, it looks like it works now
Ok, we isolated the issue, used the code again to sync the events and is not working again, it should be some kind of mispelling in the variables or the chainId, because of I changed it to the one in the variable (1337). Gotta go now @cryptokid, will continue on night or tomorrow. REALLY appretiate your help, I will be able to solve it from now <3
2 Likes
Ok @cryptokid we got this, I think 100% the solution was to sync the contract as well, because with the same code I had it is updating database correctly, I thinnk I should have done it programatically beforeā¦ haha has been a long jorney untill this point. It would have been frustrating without you guys! @alex @cryptokid Thanks a lot <3
1 Like