Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Transactions type 4 are not propagated through the network #3728

Closed
4miners opened this issue May 24, 2019 · 2 comments
Closed

Transactions type 4 are not propagated through the network #3728

4miners opened this issue May 24, 2019 · 2 comments
Assignees

Comments

@4miners
Copy link
Contributor

4miners commented May 24, 2019

Expected behavior

Transactions type 4 should be propagated to all nodes of the network.

Actual behavior

There are issues with the propagation of those transactions. When we query api/node/status endpoint on the node that we're sending transactions to, we can see that amount of pending transactions is increasing. When we query other nodes of the network, pending stays at 0 - so looks like those transactions are not propagated correctly. This also leads to block beign not full:
Screen Shot 2019-05-24 at 16 25 48

Steps to reproduce

Execute QA stress test.

Which version(s) does this affect? (Environment, OS, etc...)

2.0.0-alpha.10

@4miners 4miners changed the title Transactions type 4 are not propagated through network Transactions type 4 are not propagated through the network May 24, 2019
@SargeKhan
Copy link
Contributor

@jondubois is there a different way in which multisignature transactions are being propagated?

@4miners
Copy link
Contributor Author

4miners commented Jun 3, 2019

Closed in favor of #3624

@4miners 4miners closed this as completed Jun 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants