Create document explaining transaction rate
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- blockchain, documentation
Research direction
Start by locating the documentation structure and existing descriptions of block publication interval, block size, transaction inputs and outputs, and coin hours. Use the stated 10-second and 32 kB parameters and smallest transaction example to document the maximum and practical transaction-rate calculation. Done means the explanation covers variable transaction sizes and prioritization when the pool exceeds the block limit.
Written by the indexing model from the issue text.
Description
Transaction rate is ultimately limited by computational power and bandwidth, but there are two parameters that control the rate the network operates at:
- Block publication interval (currently 10 seconds)
- Block size (measured in bytes, currently 32kB)
These parameters are adjustable.
Transactions have variable byte size, so the block size measured in number of transactions is also variable.
If the total size of transactions in the unconfirmed pool exceeds the max block size at the time of block creation, the transactions are prioritized by the number of coin hours destroyed per byte.
Given the current parameters of 10 seconds and 32kB per block, the max transaction rate can be calculated by using the smallest possible transaction size (a transaction with one input and one output). The actual transaction rate will be less, since transactions will often have multiple inputs and two outputs (an additional output for change), increasing the average transaction size.
- Dominant language
- CSS
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fibercrypto/docs
-
Publish docs web siteMay be free again @m4yk3ldev claimed this 2490 days ago, and no pull request is open. Opendevops
fibercrypto/docs#133 · 1 assignee ·
-
Add Skycoin wiki pages for direct rendering in dev docsMay be free again @m4yk3ldev claimed this 2490 days ago, and no pull request is open. Opendevdocs skyfiber stdev wip
fibercrypto/docs#131 · 2 assignees ·
-
FiberCrypto wallet dev guide with UML diagramsMay be free again @olemis claimed this 2516 days ago, and no pull request is open. Opendevdocs wallet
fibercrypto/docs#130 · 1 assignee ·
-
Rebrand for fibercrypto forMay be free again @m4yk3ldev claimed this 2490 days ago, and no pull request is open. Openstdev wip
fibercrypto/docs#129 · 2 assignees ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
fibercrypto/docs#123 ·
All issues in fibercrypto/docs
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cline/mcp-marketplace#2727 ·
-
Price: 27 USD Priority: 3 (High) Time: <15 Minutes
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ubiquity/pay.ubq.fi#500 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cowprotocol/services#5018 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
oasisprotocol/privana#298 ·
Maintainers usually reply within 1 day