Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Allow to specify the config to include all the mempool transactions in the newly generated block #6870

Closed
LogvinovLeon opened this issue Oct 23, 2017 · 0 comments
Assignees
Labels
F8-enhancement 🎊 An additional feature request. M2-config 📂 Chain specifications and node configurations. P7-nicetohave 🐕 Issue is worth doing eventually.
Milestone

Comments

@LogvinovLeon
Copy link

I'm running:

  • Parity version: latest master
  • Operating system: MacOS
  • And installed: from source

Currently there is an option to force parity to generate a fake block with some pending transactions even if it's not mining.
--force-sealing
It grabs some transactions from the mempool and creates a fake block out of them.
It's usefull, cause later you can get pending logs by using eth_getLogs and you'll get all the logs from this fake block.
I want to have a config to make a block out of all the transactions currently in the mempool.
This way - I'll be able to see - what each of them does.

My use-case:
I have a dApp and I want my UI to update faster, then 15s after a user action. To update the UI I need to know, what will happen on the blockchain. Now I have a way to know what will happen in the next blok, but during the ICO's and other periods of network being full and mempool being much bigger then 1 block this is not very usefull, cause I might see an update after a couple of hours.
Yes, I can just fetch the transactions from the mempool, but I'll need to have a local VM running in order to get any usefull info from them. I feel like this use-case is generic enough to be supported.

@Office-Julia Office-Julia added M2-config 📂 Chain specifications and node configurations. Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. F8-enhancement 🎊 An additional feature request. and removed F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. labels Oct 24, 2017
@tomusdrw tomusdrw self-assigned this Oct 31, 2017
@5chdn 5chdn added this to the 1.9 milestone Nov 4, 2017
@5chdn 5chdn added P7-nicetohave 🐕 Issue is worth doing eventually. and removed Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. labels Nov 4, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F8-enhancement 🎊 An additional feature request. M2-config 📂 Chain specifications and node configurations. P7-nicetohave 🐕 Issue is worth doing eventually.
Projects
None yet
Development

No branches or pull requests

4 participants