-
Right now, we are showing the nonce as an hex string.
I think this should be changed as fast as possible.
The reason is, when taproot activate, we will want to move from ECDSA Adaptor sigs to Schn…
-
_From @ChristopherA on June 30, 2017 6:44_
I really like idea of using a bech32 encoded DID:BTCR as @sipa did some amazing work investing a good error detecting AND correcting encoding algorithm. ht…
-
### Area
Proposal Pillar
### Domain
preview.gov.tools
### Which wallet were you using?
_No response_
### Context
When creating a treasury proposal, the on-chain details inputs miss context
###…
Ryun1 updated
1 month ago
-
Since we use the bech32 address in std, we need to add validation regarding capitalization, else unexpected bugs will occur.
Another solution is to forgo bech32 and use a different string representat…
-
Try for example: `dgb1qf8j7y83q75x3jgfyj0d763nftwk07z2vhgg8nw`
This is a valid BECH32 address for DGB.
-
Hi! I tried to validate a litecoin bech32 address, and it fails, but the address is correct.
-
when i create a transaction, try to send bech32 address(ltc1qe7p4jney22y8lxn8zq3wt0vj9tlhqluszqsj5g). i saw a error, base58.decode error. please help!!! @coblee @wangxinxi @void-main @fancycedar @ultr…
-
Line: 13
https://github.com/ava-labs/hypersdk/blob/fd4111b44db9a3d27284a9c65e33784617428d3c/codec/address.go#L10-L20
-
Reason why it's a good idea: Native segwit addresses (Bech32) that can be recognized starting with bc1... are the new standard in Bitcoin. It reduces fees by up to ~45% compares to legacy addresses su…
-
We are trying to transfer `uusdc` to Bitcoin compatible address(bech32 style) on our blockchain, we got following error:
```
// noble
{
"chainId": "grand-1",
"txBody": {
"extensionOpti…