-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid pointer key in names/owned_by #1665
Comments
@davidyuk the keys in the pointers object are always base64-encoded, because they may be binaries |
but these keys are not encoded in the node's implementation (see first response), can you make it consistent with it? // 20240124180629
// https://testnet.aeternity.io/mdw/names/owned_by/ak_2swhLkgBPeeADxVTAVCJnZLY5NZtCFiM93JxsEaMuC59euuFRQ
{
"active": [
{
// ...
"pointers": {
"account_pubkey": "ak_2swhLkgBPeeADxVTAVCJnZLY5NZtCFiM93JxsEaMuC59euuFRQ"
},
// ...
},
{
// ...
"pointers": {
"MA==": "ak_2swhLkgBPeeADxVTAVCJnZLY5NZtCFiM93JxsEaMuC59euuFRQ"
},
// ...
},
],
"top_bid": [
]
}
what about |
@davidyuk how does the node expose binary pointer keys |
They adds ���� where necessary 🤷♀️ I've created aeternity/aeternity#4317. Let's wait till they resolve that issue. And after that, make sure the implementation is consistent. |
So, node implemented the raw bytes support in keys, please, do it the same way 🙂 |
I've claimed a name
testtesttesttest.chain
on testnet and set a pointer with key0
toak_2swhLkgBPeeADxVTAVCJnZLY5NZtCFiM93JxsEaMuC59euuFRQ
.When I'm requesting names owned by this account I'm getting in response
For some reason,
0
becameMA==
in middleware response 🤷♀️The text was updated successfully, but these errors were encountered: