Kubo RPC API unknown error: /api/v0/routing/put

Hi all,

I am using this method api-v0-routing-put without success. Probably I am doing something wrong but I am not able to find out what is it.

I don’t have any error message just this:
{
“ID”: “12D3KooWLTSofK6cdCNGjQ5Rnid1EN3Vyorcb2M6QoBsEPyf1Y6a”,
“Type”: 5,
“Responses”: null,
“Extra”: “”
}

If I use the /api/v0/name/inspect
I have got this error message:
{
“Message”: “proto: illegal wireType 6”,
“Code”: 0,
“Type”: “error”
}

I am creating the IPNS record with this function Create

So, any suggestion is welcome.


Peer ID:12D3KooWLTSofK6cdCNGjQ5Rnid1EN3Vyorcb2M6QoBsEPyf1Y6a

Agent:[kubo] [v0.20.0-dev]

arg:/ipns/12D3KooWLTSofK6cdCNGjQ5Rnid1EN3Vyorcb2M6QoBsEPyf1Y6a

IPNS name:
/ipfs/QmUfV4m2PUM559LSvDsJkoz1KofTVq25RDXwW5uMdjNb4u

IPNS record(value-file):
value:“/ipfs/QmUfV4m2PUM559LSvDsJkoz1KofTVq25RDXwW5uMdjNb4u” signatureV1:“5<w\222\224\241x\371\212\243T\362;\024/\013_#q\351F\306\333Q\021iQMRg\300\t\325\273\201\r\340\277\333\342\t\324\265\321\003\253\210\205.\005\356\270\230#\026\023?\244\014)>I+C\020\214;!\326\305\255\216\301a\034\301\t\340\331\270&\033\331\346\302s\005\342a\224\356\271\257?\024\004jqU\263\345\323\\355dBgry\261\364OQ\367\016\326\233K\271\263K\341B"\277\240\310\300,3\325)0!hC\0131\205\247(&\224\332\320\343E\316\350&\357\014\264\346<F\356\344\353\251\341\2432R’\307Y\277F\004\031\350\355\036\177\261h\351\013\371\325\202F\350\215%\010\3529\373Ax\261e\350\204\305\275fA\265\241\321\3110\305T\273\334\003c f\014W\212\347i62x\212u\250\205Bp7]\320\247\261\333\016\037\021\210\021\246\3654\231>\215\037\220\324\351)\307*\310\r\305\3471” validityType:EOL validity:“2023-03-27T10:20:01.797705473Z” sequence:0 ttl:86400000000000 signatureV2:“3>a@\022\004,\356\027\271L\270\247\261 \245P>'\3510\324w\276IcH\342\232zO_\2375\201\253\023.\241)\277\300\260a/\032cL\256 \366x\250V\371\332\026{\177\304v\032^\&|\201X\345q\310\035\256\270H\342\242-\337\236\242}\242Z^\361]\370\302\252\023.*)\252 \374\212\365\323\377)\334\331g\2558F\020\277@\315\253\361w%\363\000\355\005\316\367Kt\024Qku\027\026.\242&\362\261"\004\3024\212t\323\324\036\330G\225T\b\251\271\212\367\233A\243\260\272R\214\231y\357\215@\350?1\347\215\236\302\335\027\324\264\n\220[\002:\304\264\326\375G\007\354\270\317\357\005\332S|\301#Lv\201P\247\013\331\215\177_\322\270(\244\310\261\250\230\274v\247\024\260+\243qOWPQo\367\201\352\001\363\265\246f\236\004\177I\256OG\303\345;e\371\327s\325lG\276\247” data:“\245cTTL\033\000\000N\224\221O\000\000eValueX4/ipfs/QmUfV4m2PUM559LSvDsJkoz1KofTVq25RDXwW5uMdjNb4uhSequence\000hValidityX\0362023-03-27T10:20:01.797705473ZlValidityType\000”

This evolved into a new error:
record-public-key-does-not-match-the-verified-name

Cheers,