-
-
Hello,
It do not know if I am right, but it looks like something is wrong with the **computation of the transaction weight** (in weight units).
For instance, your explorer says that the weight…
-
**Is your feature request related to a problem? Please describe.**
Currently, ZetaChain supports passing data using the op_return opcode, which has an 80-byte limit. This limitation restricts the amo…
-
# Summary
**Add a feature to the miner to replay Stacks transactions that were part of an invalid tenure due to a Bitcoin reorg.**
Under Nakamoto, sortitions with a valid winner on the Bitcoin …
-
It would be of great help to estimate onchain fees for sending asset to an address, fields like total sats and sats/vbyte or sats/kw would help us estimate what the fees citing to number of inputs use…
-
When I build and sign a BTC transaction, it defaults to type 1. Is it possible to build and sign a type 2 BTC transaction using Wallet Core?
![image](https://github.com/trustwallet/wallet-core/assets…
-
## Proving fee
Currently we charge:
- Base fee
- Priority fee - if the user wants to pay it ofc
- L1 fee
We neglected another important fee though, proving fee.
On our latest profiling map, …
-
Hello,
I have a problem with my wallet.
I received a transaction in 2017 Same day and once confirmed there was a transaction with the same amount of btc received to another empty address. May I know…
-
One of the significant attractions of Bitcoin is that transaction data is transparent, openly available to everyone. Because it's possible to know how much Bitcoin each address holds, there arises a q…
-
By applying differential fuzzing ([bitcoinfuzz](https://github.com/brunoerg/bitcoinfuzz)) with rust-bitcoin and Bitcoin Core for block deserialization, I found out a bug during the transaction verific…