Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Congestion on the blockchain with 21 tx block free transactions #329

Closed
bpetridis opened this issue Aug 1, 2018 · 7 comments · Fixed by #500
Closed

Congestion on the blockchain with 21 tx block free transactions #329

bpetridis opened this issue Aug 1, 2018 · 7 comments · Fixed by #500
Labels
Discussion Initial issue state - proposed but not yet accepted

Comments

@bpetridis
Copy link

Created this topic to discuss potential stop-gaps that me be on the cards to address the congestion issues that have been negatively affecting the V2.0 block-chain of late. This has caused a lot of disruption especially to switcheo trading. It's not a great look.

Wanted to open the floor to potential stop gaps that may be implemented for V2.0 whilst we await the longer term release of V3.0.

Let's try keep the comments productive.

@erikzhang erikzhang added the Discussion Initial issue state - proposed but not yet accepted label Aug 1, 2018
@deanpress
Copy link

One option is for exchanges to introduce a priority GAS fee with user withdrawals so they're most likely included in the next block.

@saltyskip
Copy link

Yes Network fees are inevitable as the network continues to grow #326 is a proposal for alleviating some of the network fee pain away from users

@bpetridis
Copy link
Author

bpetridis commented Aug 12, 2018

Ideas,

  • What about increasing the configruable block size from 500 to 1000?

  • Making gas contributions mandatory for all trasnactions, even just a derived drop

  • horizontal and vertical scaling of nodes

  • implementing a detection method for spam transactions so that they are sent to the back of the queue, i know this could imply a form of censorship, but it's a protective mechanism.

@jsolman
Copy link
Contributor

jsolman commented Dec 5, 2018

I think eventually switcheo's operations will need to support fees. Congestion causing node issues will be fixed by mempool changes.

@RavenXce
Copy link
Contributor

RavenXce commented Dec 5, 2018

Switcheo already pays 0.001gas for all operations except for transferring out of contract

@RavenXce
Copy link
Contributor

RavenXce commented Dec 5, 2018

Btw we should just close the issue if it's not helpful and there are multiple other issues solving or describing the problem.

@jsolman jsolman closed this as completed Dec 6, 2018
@bpetridis
Copy link
Author

Yeah it's covered all over the place - no point keeping my initial rant open :-)

Thacryba pushed a commit to simplitech/neo that referenced this issue Feb 17, 2020
bugfix: `python m venv` -> `python -m venv`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Initial issue state - proposed but not yet accepted
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants