RNS manager works fine with 85000 https://github.com/rnsdomains/rns-manager-react/pull/317/files#diff-50f4f4b32b3437bbb15c149be31eb05dR55
As you said, do I need to pass gasPrice to solve "transaction nonce too low" error?
If this still fails, can you share with us what’s the current owner and resolver of the subdomain? And maybe some piece of code where you try to update the subdomain
Hi @KolodziejczakJa_twitter ! If you transferred the domain from address A to address B, then I guess you want B to be the controller of that domain. In that case, you just need to login to the RNS Manager (https://manager.rns.rifos.org/) with the transferred domain (make sure that your active address is B). You will be redirected to the admin page, make sure you the
Advanced mode is selected, click on the Reclaim Domain, sign the tx and then address B will become the controller of your domain
@KolodziejczakJa_twitter thanks for reaching out!
which rwallet version are you using?
Wersion 1.3.0 and try to send to domain: "openart.rsk"
Hey @KolodziejczakJa_twitter ! The domain seems to have a correct setup https://manager.rns.rifos.org/resolve?name=openart.rsk
Seems to be an rWallet issue... Can you add it to their repo? https://github.com/rsksmart/rwallet
Thanks for reaching out!! We keep in touch for any other issue :)
Hey @KolodziejczakJa_twitter ! The domain seems to have a correct setup https://manager.rns.rifos.org/resolve?name=openart.rsk
ok I add issue in their repo rsksmart/rwallet#546
Hi, @javiesses ,In my code, I'm using
rns.addr('openart.rsk') to query 'openart.rsk' with @rsksmart/rns: 1.7.4, and it returned this error, I don't figure it out...Error: No addr resolution
at D:\forgeLabs\rwallet-server\node_modules\@rsksmart\rns\lib\resolutions.js:71:15
at Generator.next (<anonymous>)
at asyncGeneratorStep (D:\forgeLabs\rwallet-server\node_modules\@rsksmart\rns\lib\resolutions.js:26:103)
at _next (D:\forgeLabs\rwallet-server\node_modules\@rsksmart\rns\lib\resolutions.js:28:194)
at process._tickCallback (internal/process/next_tick.js:68:7)
And according to returned error ref : https://developers.rsk.co/rif/rns/libs/javascript/Errors/#kb002 ,
It says
It says
The given domain has a resolver, but it does not support addr interface, how can I solve this? Thanks.
as a hint in solving the problem, I can add that this is a multi asset wallet based on the ETH address
I using Meta Mask and RSK mainnet setup to access to the wallet
Hi @tinyyxx! Please update your RNS.js library to the latest one,
1.8.2. @KolodziejczakJa_twitter set up the domain using the latest resolver, and the RNS version you are using do not support that resolver. Please take a look on the 1.8 release notes: https://github.com/rnsdomains/rns-js/releases/tag/v1.8.0
1 reply
@javiesses I've tested it with 1.8.2, and it returned
{ Error: No resolver
at _default._throw (D:\rnstest\node_modules\@rsksmart\rns\lib\errors\ErrorWrapper.js:21:11)
at D:\rnstest\node_modules\@rsksmart\rns\lib\resolutions.js:46:15
at Generator.next (<anonymous>)
at asyncGeneratorStep (D:\rnstest\node_modules\@rsksmart\rns\lib\resolutions.js:28:103)
at _next (D:\rnstest\node_modules\@rsksmart\rns\lib\resolutions.js:30:194)
at process._tickCallback (internal/process/next_tick.js:68:7)
id: 'KB003',
ref:
'https://developers.rsk.co/rif/rns/libs/javascript/Errors/#kb003' }So my code need to upgrade and his domain need to set a new resolver?
Is there any way I can still use 1.7.4 ?
Due to 1.8.2 return txHash instead of txReceipt, I have to reconstruct the logic in my rns subdomain registeration function which is a huge change..😂
Due to 1.8.2 return txHash instead of txReceipt, I have to reconstruct the logic in my rns subdomain registeration function which is a huge change..😂
1 reply
how about using web.eth.getTransactionReceipt using the txHash? https://web3js.readthedocs.io/en/v1.2.11/web3-eth.html#gettransactionreceipt it's a one liner and you wouldn't have to change the logic
5 replies
what is new resolver addres ?
I was wondering what makes RIF/RNS superior to Namecoin?
if I understand correctly, RNS is much more vulnerable to disruption in the parent chain. E.g. Namecoin was pretty much unaffected by the Bitcoin/BCH hashwar, while Rootstock would have been severely disrupted by it
(to purchase .rsk domain)
So does anyone actually answer questions here I see messages from November (!!) that appear to be unanswered....
Ot did y'all make your coin millions and now just kickin' it in the Caribbean? ;)
ok