Waves Dev Jedi | RIDE for dApps

13 Jan 2025 16:58

Yes, it can be used.

Waves Dev Jedi | RIDE for dApps

13 Jan 2025 11:42

In my explorer i calculate burn fees as cumulative (across all transactions in a block) value which goes to meta address BURNER: https://unit0.w8.io/BURNER

Waves Dev Jedi | RIDE for dApps

13 Jan 2025 11:40

https://eips.ethereum.org/EIPS/eip-1559

Waves Dev Jedi | RIDE for dApps

13 Jan 2025 11:21

For UNIT0 biz dev, please help me about UNIT0 burning.

My statement:
"UNIT0 fees are burned, but there is no burn wallet"

In explorer, I only see burnt fees, no transfer tx to a 'burn wallet'

Listing party:
"Could you clarify where the tokens go then? There must be a wallet; otherwise, it’s impossible to prove the burn."

Waves Dev Jedi | RIDE for dApps

12 Jan 2025 23:11

Hello, I buy pi coins at $150 per pi and I make payment first, Message me if you have.

Waves Dev Jedi | RIDE for dApps

12 Jan 2025 16:45

Waves is 64 bit precision (https://docs.waves.tech/en/blockchain/token/#custom-token-parameters look for quantity). If you need more precision, you can do it by some smart contract development, as it has 512 bit precision via BigInts (https://docs.waves.tech/en/ride/data-types/bigint). Native platform tokens does not fit your needs if you have more than 64 bit numbers.

Waves Dev Jedi | RIDE for dApps

12 Jan 2025 05:44

Hi, everyone. I am building my own Project and need someone's development assistant to update.
Please DM, I want your help.

Waves Dev Jedi | RIDE for dApps

11 Jan 2025 14:25

Hi, everyone. I am building my own Project and need someone's development assistant to update.
Please DM, I want your help.

Waves Dev Jedi | RIDE for dApps

11 Jan 2025 08:28

Any blockchain developer here?
Dm me

Waves Dev Jedi | RIDE for dApps

10 Jan 2025 11:15

Then I will try to find and understand the transfer implementation from here

Waves Dev Jedi | RIDE for dApps

10 Jan 2025 09:43

I thought we should hash it. OK, but it still doesn't work.

const txBody: Buffer = createTransferBody(trxData);
const signature: Uint8Array = sign(bs58.decode(privateKeys[sender]), txBody);

Waves Dev Jedi | RIDE for dApps

10 Jan 2025 01:43

in general, that's what I was doing. But I rewrote the code from php to ts, wrote a simplified version with hardcore, it still doesn't work. That is really strange. Will think

Waves Dev Jedi | RIDE for dApps

10 Jan 2025 00:01

I can provide PHP code example of that you are doing.

Typical transfer transaction as json: https://github.com/deemru/WavesKit/blob/7c3e536a8f8c9591e4738028aaea5735d14c1d08/src/WavesKit.php#L1780-L1798

And as bytes: https://github.com/deemru/WavesKit/blob/7c3e536a8f8c9591e4738028aaea5735d14c1d08/src/WavesKit.php#L2310-L2323

Waves Dev Jedi | RIDE for dApps

09 Jan 2025 23:58

Where do you get such fields? attachmentLen? attachmentBytes?

Take any valid transfer as a reference, for example: http://nodes.wavesnodes.com/transactions/info/3XFDy1BDWW3FrticQpEuHKiMdVCuQ3dcVEcnHGusBdsV

Waves Dev Jedi | RIDE for dApps

09 Jan 2025 23:41

Pass to serialization endpoint version = 2 and to broadcast version = 2

Waves Dev Jedi | RIDE for dApps

13 Jan 2025 16:49

CAN THE PYWAVES LIBRARY STILL BE USED?

Waves Dev Jedi | RIDE for dApps

13 Jan 2025 11:41

Calculation by tx: https://github.com/deemru/w8io-ethereum/blob/21ded9a683a96734e070affb0ae7af2a5c95426d/include/BlockchainParser.php#L380

Waves Dev Jedi | RIDE for dApps

13 Jan 2025 11:21

Example tx: https://explorer.unit0.dev/tx/0xbcfcfd72ef873dd5b1292fbb3b0c8ba468f82243b581b51a3d4349003d936c1b?tab=index

Waves Dev Jedi | RIDE for dApps

13 Jan 2025 09:54

Any blockchain developer here?
Dm me

Waves Dev Jedi | RIDE for dApps

12 Jan 2025 16:46

When you work with BigInt it is passed as String then https://docs.waves.tech/en/ride/functions/built-in-functions/converting-functions#parsebigint-string-bigint-unit

Waves Dev Jedi | RIDE for dApps

12 Jan 2025 16:01

I made amount a string first, and where necessary, I turn it into a Big one. Now the bytes match, but the transaction cannot be sent. The endpoint expects me to pass a number, not a string. And how to do it without loss in this case? You can't send a big number, you can't send a string. Pass the Number, but there will be a loss of accuracy. UNSOLVABLE

Waves Dev Jedi | RIDE for dApps

11 Jan 2025 20:58

hello, i'm a senior full stack and blockchain developer. how can help you?

Waves Dev Jedi | RIDE for dApps

11 Jan 2025 13:33

Ask your related question here

Waves Dev Jedi | RIDE for dApps

11 Jan 2025 00:30

i done it. Thank you, Дмитрий!
I needed this link, which I ignored for some reason
https://docs.waves.tech/ru/blockchain/binary-format/transaction-binary-format/transfer-transaction-binary-format#версия-2

Waves Dev Jedi | RIDE for dApps

10 Jan 2025 09:47

Yes.

If something does not work, please use already known to work libs and go step-by-step finding at which step is the difference.

Waves Dev Jedi | RIDE for dApps

10 Jan 2025 07:51

Signature of tx is a signature of txBody, not txHash

Waves Dev Jedi | RIDE for dApps

10 Jan 2025 00:03

Thank you very much, I'll figure it out

Waves Dev Jedi | RIDE for dApps

10 Jan 2025 00:00

Do not guess, you can use any libs to understand things and then make your own.

Waves Dev Jedi | RIDE for dApps

09 Jan 2025 23:50

but it doesnt work to

Waves Dev Jedi | RIDE for dApps

09 Jan 2025 23:41

If you do version 2, why you add version 3?