QA:

Looks good. Idk if it's worth it to also log the onchain function name that was called too using the 4byte api .. @rndquu rfc

I think if we can make this robust and re-useable @ariesgun then we can open a task and implement it in rpc-handler as core error handling. That might be a task you'd like to complete if so.

Expected behavior: user sees a toaster with a human friendly error instead of a hex string.

It should be made clear in the spec.

Unused dependencies (1)

Unlisted dependencies (2)

For now, waiting for the ubiquite-hosted npm package for ethers-decode-error to be created.

I opened a PR on that regard here: ubiquity/ethers-decode-error#1
@0x4007 after thought, should I create it there or in ubiquity-os

I suppose all crypto related software should be under ubiquity org.

@ariesgun, this task has been idle for a while. Please provide an update.

Still ongoing

@ariesgun, this task has been idle for a while. Please provide an update.

I had implemented our own ethers-decode-error but every time the publish fails:
https://github.com/ubiquity/ethers-decode-error/actions/runs/11735404423/job/32693050614#step:7:21

@ariesgun Did you manually publish it? If so I do not have the NPM token myself and @0x4007 should publish it manually. If not let me know how you proceeded.

I had implemented our own ethers-decode-error but every time the publish fails: https://github.com/ubiquity/ethers-decode-error/actions/runs/11735404423/job/32693050614#step:7:21

@ariesgun Did you manually publish it? If so I do not have the NPM token myself and @0x4007 should publish it manually. If not let me know how you proceeded.

yes, I did it manually

@ariesgun, this task has been idle for a while. Please provide an update.

@ariesgun, this task has been idle for a while. Please provide an update.

Still waiting for the package to be uploaded

@0x4007 You are the one with NPM credentials if you can please publish the package.

@0x4007 You are the one with NPM credentials if you can please publish the package.

Isn't NPM_TOKEN relevant? The latest release workflow silently failed with The local branch 1.x is behind the remote one, therefore a new version won't be published. . Should we publish manually first or there's smth wrong with the package.json?

@rndquu yeah I tried several times:
#353 (comment)

Either we should change the workflow, either manually publish because it seems to compare the version to the main forked repo so we cannot make any modification and publish it. We could copy the publishing action we usually use for our other projects.

@ariesgun, this task has been idle for a while. Please provide an update.

@rndquu yeah I tried several times: #353 (comment)

Either we should change the workflow, either manually publish because it seems to compare the version to the main forked repo so we cannot make any modification and publish it. We could copy the publishing action we usually use for our other projects.

Is there anything I can do to finalize this PR? As far as I understand, the package has not been uploaded yet due to token issue?

I published it under ubiquity-os: https://www.npmjs.com/package/@ubiquity-os/ethers-decode-error @ariesgun please try using this package.

@rndquu You can delete this repo: https://github.com/ubiquity/ethers-decode-error thank you.

I published it under ubiquity-os: https://www.npmjs.com/package/@ubiquity-os/ethers-decode-error @ariesgun please try using this package.

@rndquu You can delete this repo: https://github.com/ubiquity/ethers-decode-error thank you.

The crypto related stuff should be under @ubiquity

@0x4007 Please move it because I have no access and the NPM token under ubiquity seems to be invalid to publish packages, or at least I don't know what is expected, maybe ubiquibot/ethers?
https://github.com/ubiquity/ethers-decode-error/actions/runs/12107146609/job/33753718023#step:6:58

That's right we might not have access to the ubiquity npm for some reason. @rndquu im mobile but do you have access? Can you solve for this

Is there anything I can do to help close this one?

@rndquu @gentlementlegen lets finalize this

@0x4007 Please move it because I have no access and the NPM token under ubiquity seems to be invalid to publish packages, or at least I don't know what is expected, maybe ubiquibot/ethers? https://github.com/ubiquity/ethers-decode-error/actions/runs/12107146609/job/33753718023#step:6:58

@0x4007 would need the token to be updated in order to publish to the proper NPM organization.

As far as I understand everything is fine right now:

• https://github.com/ubiquity-os/ethers-decode-error is hosted in the ubiquity-os organization
• https://www.npmjs.com/package/@ubiquity-os/ethers-decode-error is hosted under the @ubiquity-os organization on npm
• the PR works fine