[Error] signatureId must be shorter than or equal to 24 characters
See original GitHub issuetransaction = await deployNFT(useTestNet,
{
name,
chain: "MATIC",
symbol,
provenance: true,
publicMint: false,
signatureId: 'a4873cd9-...........-7074056db3c4'
});
Response with error:
signatureId must be shorter than or equal to 24 characters
Using the endpoint API with same payload works ok. signatureId validation should change to 36 characters same as the API.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Why your password can't have symbols—or be longer than 16 ...
The brokerage and banking company Charles Schwab has strict length limits—passwords can be no longer than eight characters, no shorter than ...
Read more >Understanding and Configuring Snort Rules | Rapid7 Blog
In this article, we will learn the makeup of Snort rules and how we can we configure them on Windows to get alerts...
Read more >"Too many characters in character literal error" - Stack Overflow
A char can hold a single character only, a character literal is a single character in single quote, i.e. '&' - if you...
Read more >Documentation: 15: 8.3. Character Types - PostgreSQL
If the string to be stored is shorter than the declared length, ... the length must be greater than zero and cannot exceed...
Read more >Remedy & ITSM Error Message Lookup - ARE|RRR - rrr.se
Level Number Subject
NOTE 32 AR System server terminated normally.
ARERR 49 Internal error: The request ID is invalid.
WARNING 50 You have no permission to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Problem here is following - all
*/broadcast
endpoints accept optional singatureId parameter - which should be 24 chars long ID of the transaction, which is signed inside Tatum KMS and should be marked as completed on Tatum side. You should not directly call those endpoints with your own signatureId. I will double check the implementation inside V1 SDK, if there is proper validation present. @belguithFixed 😄 😄 may thanks @samuelsramko