Looking at the serialization endpoint, I fixed my transaction serialization and now it generates the correct byte sequence. However, if you do not specify version 3 in the sent json, the node will automatically substitute the wrong version 1. After I have signed the bytes, I send a json transaction to the endpoint, adding a version 3 field to it: (watch the screenshot)
That is, the bytes of the version were not taken into account when signing. Should I specify version bytes in the signature? I think not, it is not given in the documentation (the table above). In the end, I get all the same error.

Читать полностью…

So it is from wavesplatform, as waves-transactions, i do not get it. Why you writing your own serialization?

Читать полностью…

How can you avoid third-party with keccak256/blake2b/curve25519 signing? Are you writing your own signature/hash from scratch??

Читать полностью…

I already pointed where your error is. In serialization (or version). And you have the endpoint to check your serialization is correct. Then you fix you can try to sign again.

Читать полностью…

Tried this lib? A bit outdated, but still
https://github.com/wavesplatform/waves-transactions

Читать полностью…

I pointed to serialization endpoint not broadcasting ^

Читать полностью…

I think you did version 2

Читать полностью…

I tried to make a byte-by-byte transaction, as in the documentation

typescript 
const txDataBytes = new Uint8Array(91);

      txDataBytes[0] = txData.type;
      txDataBytes.set(bs58.decode(txData.senderPublicKey), 1);
      txDataBytes[33] = txData.amountAssetFlag;
      txDataBytes[34] = txData.feeAsset;
      txDataBytes.set(new Uint8Array(new BigInt64Array([BigInt(txData.timestamp)]).buffer), 35);
      txDataBytes.set(new Uint8Array(new BigInt64Array([BigInt(txData.amount)]).buffer), 43);
      txDataBytes.set(new Uint8Array(new BigInt64Array([BigInt(txData.fee)]).buffer), 51);
      txDataBytes.set(bs58.decode(txData.recipient), 59);
      txDataBytes[85] = txData.attachmentLen;
      txDataBytes.set(new Uint8Array(txData.attachmentBytes), 87);

const txDataBuffer: Buffer = Buffer.from(txDataBytes);

txData - an item without a signature

Читать полностью…

txDataBuffer?

Читать полностью…

If you have real question, not potential - ask them here. This is the purpose of this chat

Читать полностью…

https://youtu.be/WOh32CUxm84

1:21:08

Читать полностью…

Responsible? I think he is in charge of the core team, but many flows switched to decentralized approaches via https://app.power.tech/ and https://dao.unit0.dev/

Читать полностью…

You should mention this (master is usable and not outdated) info at least in readme. Glad to hear this.

Читать полностью…

Exactly as i told. And as every developer see it.

Читать полностью…

Thank for the verbose answer! I will try it.

Читать полностью…

for educational purposes, I was given this task. Without using third-party dependencies (only if copying, but not importing), write functions for creating a txBuild transaction, signing a txSign, and sending it to the network

Читать полностью…

i use ( ctrl c + ctrl v )
https://github.com/wavesplatform/curve25519-js

Читать полностью…

I'll try to figure it out and write to you again. Thank you so much for such quick feedback!

Читать полностью…

my task is to avoid using third-party libraries. :(As a last resort, I'll try to send a transaction through this library, and figure out its code so that I don't end up using it.

Читать полностью…

Version 3 transfer transaction is protobuf like (serialization)

Читать полностью…

after this error, I turned to you!

Читать полностью…

You can always check yourself here: http://nodes.wavesnodes.com/api-docs/index.html#/utils/serializeTx

Читать полностью…

If you are doing some your own code for signing Waves transactions, this is the best reference to start: https://docs.waves.tech/en/blockchain/waves-protocol/cryptographic-practical-details

Читать полностью…

Hi @deemru! Yesterday I scrolled through a lot of questions on the 2018-2019 forum, and you actively answered there, it was unexpectedly nice to find you here! I need your help. In my app, I am trying to sign a transfer transaction, but I encounter error 112 invalid signature. I collected the necessary bytes exactly according to the documentation, hashed them using keccak + blake

      const txHash: Buffer = createKeccakHash('keccak256').update(blake2b256(txDataBuffer)).digest();

, and signed them using a private key and curve25519. I think the problem may be that I am sending the wrong json structure. Here is one of the options that I sent:
{
type: 4,
version: 3,
sender: '3PLYHmpVK9T5tQSTUf3W7wz8vT7RwyeCqr7',
senderPublicKey: 'GHkVCQTEEBiagP1ikpEut4pTWj1gKcqCePkp9esMJqY4',
recipient: '3PHPyhDzeMNSKQiXAG3zJp3dB1D3MkDkdVF',
amount: 500000,
fee: 100000,
timestamp: 1736429211225,
attachment: '',
proofs: [
'9BVzCWAwRF4DDqbVBuRArFmqxdF1K8bipPC6YC9y3iHptorDLfA47w5r7ntu3AUtvw4hhrEaXQpgyF1JMw8qjNh'
],
chainId: 87
}
ps: можно перейти на русский )

Читать полностью…

Hello everyone,

I am Archimedian, the founder of the MCE token recently deployed on the Waves blockchain.
Our project aims to create a financing tool for energy projects worldwide.

I would like to be connected with a representative or administrator to discuss potential questions I have regarding the platform.

For more information, feel free to visit our website: mkfinanceshome.com
Alternatively, you can contact me directly via private message.

Best regards,
Archimedian

Читать полностью…

In the recent interview he said that he sold all his WAVES, that's why I am asking

Читать полностью…

Is Sasha still responsible for the ecosystem?

Читать полностью…

Ok. As you wish. We will make release as soon as possible. But I want to inform you that our master is always usable/tested.

Читать полностью…

Fell free to ask me anything about go version.

Читать полностью…

You can try, nothing bad happened. But you have to build from master. The release is quite old.

Читать полностью…