V28 Nano-Docs Update (#717)

* Create release-v28-0.md

Add basic v28 release page

* Update node-releases.md

Adding v28 to current/active release documentation

* Create release-details-v29-0.md

Creating v29 release details stub

* Update release-details-v28-0.md

* Update mkdocs.yml

Adding V28 navigation links

* Update main.html

Adding V28.0 announcement banner

* Update current-build-links-main.md

Adding V28 links

* Update current-build-links-test.md

Adding V28 test links

* Update release-details-v27-0.md

Adding V27.0 release date

* Update release-details-v27-1.md

Adding V27.1 release date

* Update spam-work-and-prioritization.md

Adding V28 spam resistance improvements to the table

* Update release-v28-0.md

Adding V28 release info to mirror the official blog post.

* Update release-v28-0.md

Updated known issues, added information for RPC changes

* Update rpc-protocol.md w/ deprecation note for old conversion RPCs

Adding additional deprecation note for old conversion RPCs

* Update release-v28-0.md

Add link to alternative unit conversion RPCs

* Update release-v28-0.md

Adding additional RPC changes & major updates (vote rebroadcast improvements & the fork_cache addition)

* Update rpc-protocol.md

Adding v28 RPC update info:
- include_linked_account parameter was added to the account_history, block_info, and blocks_info
- bootstrap_reset
- bootstrap_priorities

* Update spam-work-and-prioritization.md

Adding vote rebroadcaster filtering

* Update toml-config-commands.md w/ --update_config

* Update release-v28-0.md w/ config changes section

* Update release-v28-0.md

Fixing broken snippet link

* Update release-v28-0.md (reorder sections)

Reordering sections

* Update release-v28-0.md w/ CLI doc link for toml configs

Adding additional detail links for the config change section

* Update release-v28-0.md

---------

Co-authored-by: Piotr Wójcik <3044353+pwojcikdev@users.noreply.github.com>

Author: qwahzi

docs/commands/rpc-protocol.md

@@ -126,7 +126,8 @@ If the `count` limit results in stopping before the end of the account chain, th
 **Optional parameters:**
 
 - `raw` (bool): if set to `true` instead of the default `false`, instead of outputting a simplified send or receive explanation of blocks (intended for wallets), output all parameters of the block itself as seen in block_create or other APIs returning blocks. It still includes the "account" and "amount" properties you'd see without this option.  State/universal blocks in the raw history will also have a `subtype` field indicating their equivalent "old" block. Unfortunately, the "account" parameter for open blocks is the account of the source block, not the account of the open block, to preserve similarity with the non-raw history.   
-- `head` (64 hexadecimal digits string, 256 bit): instead of using the latest block for a specified account, use this block as the head of the account instead. Useful for pagination.   
+- `head` (64 hexadecimal digits string, 256 bit): instead of using the latest block for a specified account, use this block as the head of the account instead. Useful for pagination.
+- `include_linked_account` (bool): _version 28.0+._ When set to `true`, the response will include a new field `linked_account`, which returns the linked account associated with the block (or "0" if no linked account exists/was found e.g. due to pruning).
 - `offset` (decimal integer): skips a number of blocks starting from `head` (if given). Not often used. _Available since version 11.0_    
 - `reverse` (bool): if set to `true` instead of the default `false`, the response starts from `head` (if given, otherwise the first block of the account), and lists blocks up to the frontier (limited by "count"). **Note**: the field `previous` in the response changes to `next`. _Available since version 19.0_  
 - `account_filter` (array of public addresses): results will be filtered to only show sends/receives connected to the provided account(s). _Available since version 19.0_. **Note:** In v19.0, this option does not handle receive blocks; fixed in v20.0.
@@ -894,6 +895,13 @@ Note: The `Balance` in contents is a uint128. However, it will be a hex-encoded
 _version 19.0+_  
 Default "false". If "true", "contents" will contain a JSON subtree instead of a JSON string.
 
+
+**Optional `include_linked_account`**
+
+_version 28.0+_
+(bool):  When set to `true`, the response will include a new field `linked_account`, which returns the linked account associated with the block (or "0" if no linked account exists/was found e.g. due to pruning).
+
+
 ---
 
 ### blocks  
@@ -978,6 +986,11 @@ Using the optional `json_block` is recommended since v19.0.
   }
 }
 ```
+**Optional `include_linked_account`**
+
+_version 28.0+_
+(bool): When set to `true`, the response will include a new field `linked_account`, which returns the linked account associated with the block (or "0" if no linked account exists/was found e.g. due to pruning).
+  
 **Optional "pending", "source"**
 
 _pending, source: version 9.0+_  
@@ -1173,6 +1186,32 @@ String, empty by default. Set specific ID for new bootstrap attempt for better t
 
 ---
 
+### bootstrap_priorities  
+_version 28.0+_   
+Dumps info about priority and blocking sets to aid in debugging any potential problems
+
+**Request:**
+```json
+{
+  "action": "bootstrap_priorities"
+}
+```  
+
+---
+
+### bootstrap_reset  
+_version 28.0+_   
+Resets ascending bootstrap state - both priority and blocking sets are cleared.
+
+**Request:**
+```json
+{
+  "action": "bootstrap_reset"
+}
+```  
+
+---
+
 ### bootstrap_status  
 _version 17.0+_
 
@@ -1417,7 +1456,7 @@ If the block is unknown on the node, the following error will be returned:
 
 ### confirmation_info 
 _version 16.0+_   
-Returns info about an unconfirmed active election by **root**. Including announcements count, last winner (initially local ledger block), total tally of voted representatives, concurrent blocks with tally & block contents for each. Using the optional `json_block` is recommended since v19.0.
+Returns info about an unconfirmed active election by **root**. Including announcements count, last winner (initially local ledger block), total tally of voted representatives, concurrent blocks with tally & block contents for each. Using the optional `json_block` is recommended since v19.0. Updated in v28.0 to include a list of representatives_final (representatives that have voted with final votes). 
 
 !!! note
     The roots provided are two parts and differ between the first account block and subsequent blocks:
@@ -4602,6 +4641,9 @@ Deprecated in V24.0+. Replaced by [accounts_receivable](#accounts_receivable)
 ---
 
 ### krai_from_raw   
+
+Deprecated in V28.0+. For alternatives, see [Unit Conversion RPCs](#unit-conversion-rpcs)
+
 Divide a raw amount down by the krai ratio.  
 
 **Request:**
@@ -4621,6 +4663,9 @@ Divide a raw amount down by the krai ratio.
 ---
 
 ### krai_to_raw    
+
+Deprecated in V28.0+. For alternatives, see [Unit Conversion RPCs](#unit-conversion-rpcs)
+
 Multiply an krai amount by the krai ratio.  
 
 **Request:**
@@ -4640,6 +4685,9 @@ Multiply an krai amount by the krai ratio.
 ---
 
 ### mrai_from_raw    
+
+Deprecated in V28.0+. For alternatives, see [Unit Conversion RPCs](#unit-conversion-rpcs)
+
 Divide a raw amount down by the Mrai ratio.  
 
 **Request:**
@@ -4659,6 +4707,9 @@ Divide a raw amount down by the Mrai ratio.
 ---
 
 ### mrai_to_raw    
+
+Deprecated in V28.0+. For alternatives, see [Unit Conversion RPCs](#unit-conversion-rpcs)
+
 Multiply an Mrai amount by the Mrai ratio.  
 
 **Request:**
@@ -4678,6 +4729,9 @@ Multiply an Mrai amount by the Mrai ratio.
 ---
 
 ### rai_from_raw    
+
+Deprecated in V28.0+. For alternatives, see [Unit Conversion RPCs](#unit-conversion-rpcs)
+
 Divide a raw amount down by the rai ratio.  
 
 **Request:**
@@ -4697,6 +4751,9 @@ Divide a raw amount down by the rai ratio.
 ---
 
 ### rai_to_raw   
+
+Deprecated in V28.0+. For alternatives, see [Unit Conversion RPCs](#unit-conversion-rpcs)
+
 Multiply an rai amount by the rai ratio.  
 
 **Request:**

docs/protocol-design/spam-work-and-prioritization.md

@@ -21,6 +21,7 @@ Below is a list of some of Nano's key spam mitigation features.
 | [Balance tiers (buckets)](https://github.com/nanocurrency/nano-node/pull/3208) | As of V27, there are 63 balance tiers (buckets) that nodes rotate through in a round-robin manner. Spamming a single bucket (e.g. Ӿ0.0001) has minimal impact on accounts in other buckets (e.g. Ӿ1, Ӿ5, etc). See [prioritization details](#prioritization-details) below. | V22+ |
 | [Bootstrap limits](https://github.com/nanocurrency/nano-node/pull/4158) | Configurable ascended bootstrapper limits via requests_limit, database_requests_limit, pull_count, timeout, [bootstrap_bandwidth_limit](https://github.com/nanocurrency/nano-node/blob/develop/nano/node/nodeconfig.hpp#L129-L130), [bootstrap_connections_max](https://github.com/nanocurrency/nano-node/blob/develop/nano/node/nodeconfig.hpp#L100-L101), etc. Default outbound bootstrap traffic limit is 5MB/s. Default max incoming bootstrap connections count is 64 (lower values save IOPs & bandwidth). | V25+ |
 | [Bounded active election buckets](https://github.com/nanocurrency/nano-node/pull/4626) | Limits election bucket size and allows for dynamically dropping and scheduling higher priority elections. Buckets can be configured to opportunistically use more available space if AEC is underutilized. | V27+ |
+| [Bounded block backlog](https://github.com/nanocurrency/nano-node/pull/4787) | Implements limits on unconfirmed transaction storage and processing, which helps ensure consistent confirmation rates during high network load and prevents resource exhaustion attacks. | V28+ |
 | [Bounded unchecked memory table](https://github.com/nanocurrency/nano-node/pull/3835) | Add a memory container for unchecked blocks once the initial bootstrap threshold is reached, with blocks pruned in FIFO order. Limited to two items per dependency. | V23.3+ |
 | [Fair queueing](https://github.com/nanocurrency/nano-node/pull/4476) | Each peer (node) & each component (e.g. [block processor](https://github.com/nanocurrency/nano-node/pull/4476), [vote processor](https://github.com/nanocurrency/nano-node/pull/4536), [bootstrap server](https://github.com/nanocurrency/nano-node/pull/4584), [request aggregator](https://github.com/nanocurrency/nano-node/pull/4598), etc) gets its own small queue with a configurable size & priority. Nodes process these queues in a (weighted) round robin manner. This ensures that even when network is under stress, data coming from well-behaved peers is ingested quickly. | V27+ |
 | [Final vote replies](https://github.com/nanocurrency/nano-node/pull/4648) | For blocks that are marked as final or confirmed, nodes will only respond with final votes (not non-final votes). This signficantly reduces network (specifically voting) traffic. | V27+ |
@@ -35,7 +36,11 @@ Below is a list of some of Nano's key spam mitigation features.
 | [Prevent requeuing of blocks with invalid signatures](https://github.com/nanocurrency/nano-node/pull/4130) | Requeueing of blocks with invalid signatures during lazy bootstrapping is not needed, since an invalid signature will always be invalid and doesn't need to be bootstrapped again. | V25+ |
 | [Proof-of-Work](https://github.com/nanocurrency/nano-node/blob/develop/nano/lib/work.cpp) | Each Nano transaction requires a small Proof-of-Work. | All
 | [Rep crawler overhaul](https://github.com/nanocurrency/nano-node/pull/4449#issuecomment-1968919321) | Consistently find representatives, even when vote requests are unreliable | V27+ |
+| [Traffic Shaping](https://github.com/nanocurrency/nano-node/pull/4786) | Enables more equal distribution of network resources among peers & proactively manages network traffic to help prevent congestion. | V28+ |
 | [Vote by hash](https://github.com/nanocurrency/nano-node/pull/1025) | Instead of voting with a full block (256 bytes), representatives vote with block hashes (32 bytes), and batch these hashes. As of V27, nodes can vote for up to [255 hashes](https://github.com/nanocurrency/nano-node/pull/4683) in a single vote. | V15+ |
+| [Vote Distribution Optimization](https://github.com/nanocurrency/nano-node/pull/4766) | Separate vote flooding patterns for PRs and non-PRs, to ensure votes are distributed more efficiently. | V28+ |
+| [Vote Filtering](https://github.com/nanocurrency/nano-node/pull/4735) | Filters out vote duplicates early on during packet processing. | V28+ |
+| [Vote Rebroadcaster Filtering](https://github.com/nanocurrency/nano-node/pull/4849) | An index that tracks and filters vote rebroadcasts. Includes: tracking the top 100 reps by weight, per-rep history of recent votes & block hashes, deduplicating by vote hash, minimum time interval between rebroadcasts of the same hash from the same rep. | V28+ |
 | [(Future) Additional improvements](https://github.com/nanocurrency/nano-node/issues/4262) | See list of potential future improvements that have been noted for additional research. | Future |
 
 ## Work algorithm details

docs/releases/node-releases.md

@@ -11,7 +11,7 @@ Updates to the Nano protocol are done through major node releases, occurring app
 ## Current Release
 The following release is the latest and only release actively supported by the Nano Foundation. This release and the [Active Releases](#active-releases) below represent the only node versions that will participate on the main network. More details can be found on the [Current Release Notes page](/releases/current-release-notes).
 
---8<-- "release-details-v27-1.md"
+--8<-- "release-details-v28-0.md"
 
 **Builds and Commands**
 
@@ -22,7 +22,7 @@ The following release is the latest and only release actively supported by the N
 ## Next Planned Release
 The following release is currently under development. Details about potential features to be included can be found in the [Nano Roadmap GitHub Project](https://github.com/orgs/nanocurrency/projects/27).
 
---8<-- "release-details-v28-0.md"
+--8<-- "release-details-v29-0.md"
 
 --8<-- "setup-beta-test-testing.md"
 
@@ -31,6 +31,10 @@ The following release is currently under development. Details about potential fe
 ## Active Releases
 The following releases can still actively participate on the network by peering with other nodes of the same versions. Any nodes running versions earlier than these will no longer peer with the latest and fall out of sync with the network.
 
+--8<-- "release-details-v28-0.md"
+
+---
+
 --8<-- "release-details-v27-1.md"
 
 ---

docs/releases/release-v28-0.md

@@ -0,0 +1,115 @@
+title: Release notes - V28.0 nano node
+description: Details of the V28.0 nano node release.
+
+# V28.0
+
+--8<-- "release-details-v28-0.md"
+
+---
+
+## Major updates
+
+### Bounded Block Backlog
+
+The Bounded Block Backlog (BBB) adds a maximum limit for unconfirmed transactions (currently 100,000), helping prevent resource exhaustion attacks & ensuring more consistent confirmation rates during high network load.
+
+### Traffic Shaping
+
+Traffic shaping complements the fair queuing system implemented in V27, by managing outbound network traffic more intelligently. This helps ensure more equal distribution of bandwidth between peers, reduces network congestion, & helps maintain performance during peak network usage.
+
+### RocksDB Optimizations
+
+Nano's RocksDB implementation has been updated to V9.7.2, and the default configuration settings have been updated to match current best practices. Additionally, a range of improvements related to memory usage, thread handling, & lock management have been included, improving stability and performance for nodes using the RocksDB database backend.
+
+### Vote Generation Improvements
+
+The vote generation system has been redesigned to be more resource-efficient, reducing CPU usage, improving priority vote processing, & bundling votes more intelligently. 
+
+### Vote Filter Implementation
+
+A new vote filter implements sophisticated deduplication and relevancy checks, eliminating redudant votes, reducing bandwidth usage, lowering memory usage, & reducing overall network load. 
+
+### Vote Rebroadcasting Overhaul
+
+The vote_rebroadcaster component was overhauled, making vote rebroadcasting smarter & more efficient. Previously we used a simple queue with a naive filter which rebroadcasted all processed votes. Since a vote can contain up to 255 hashes and the same vote can be processed multiple times depending on the exact timing of election activation, this introduced a rather significant inefficiency where we could rebroadcast the same vote multiple times, wasting bandwidth. The vote rebroadcaster overhaul significantly improves this by improving tracking & filtering of vote rebroadcasts.
+
+### Bootstrap & Database Optimizations
+
+Bulk frontier scanning has been added to the ascending bootstrapper, processing up to 1,000 accounts simultaneously. I/O overhead has also been reduced through smart caching and optimised database queries. Additionally, a new `fork_cache` & block bootstrapping improvements were added, speeding up fork resolution during certain bootstrap scenarios.
+
+### Legacy Code Removal
+
+The legacy bootstrapper has been completely removed, simplifying the codebase & improving code maintability.
+
+### Bug fixes
+
+Several bugs were fixed, including race conditions, missing notifications, & dependency issues.
+
+---
+
+## Upgrade notices
+
+### RPC changes
+
+#### Bootstrap RPCs
+
+The following bootstrap related RPC commands have been extended, modified, or added:
+
+* `bootstrap_status`: previously this returned the status of legacy bootstrap; modified to return the status of ascending bootstrap
+* `bootstrap_reset`: resets ascending bootstrap state, both priority and blocking sets are cleared
+* `bootstrap_priorities`: dumps info about priority and blocking sets to aid in debugging any potential problems
+
+Please note that the above bootstrap RPC commands are internal/diagnostic RPCs, & may not be stable.
+
+#### Confirmation_info RPC
+
+This is a backwards compatible change that updated the `confirmation_info` RPC call to include a list of `representatives_final` (representatives that have voted with final votes). Thanks to MajorChump for submitting this PR!
+
+#### Ratio & Conversion related RPCs
+
+Xrb_ratio has been removed and replaced with nano_ratio:
+
+| Existing name | ratio | Value | New name |
+|---------------|-------|-------|----------|
+| Gxrb_ratio | 10^33 | 1000 nano | Knano_ratio |
+| Mxrb_ratio | 10^30 | 1 nano | nano_ratio |
+| kxrb_ratio | 10^27 | 0.001 nano | __removed__ |
+| xrb_ratio | 10^24 | 0.000001 | __removed__ |
+ 
+The following deprecated RPC endpoints for conversion have been removed:
+* `krai_from_raw`
+* `krai_to_raw`
+* `mrai_from_raw`
+* `mrai_to_raw`
+* `rai_from_raw`
+* `rai_to_raw`
+
+For alternatives, see [Unit Conversion RPCs](../commands/rpc-protocol.md#unit-conversion-rpcs)
+
+#### Other RPC Changes
+
+An optional `include_linked_account` parameter was added to the `account_history`, `block_info`, and `blocks_info` RPC endpoints. When enabled, the response will include a new field `linked_account`, which returns the linked account associated with the block (or "0" if no linked account exists/was found e.g. due to pruning). Thanks to Exxenoz for submitting this PR!
+
+### Config changes
+
+While the previous toml for database backend configuration is still supported for now, it is being replaced by `database_backend = "lmdb"` or `database_backend = "rocksdb"` under `[node]`.
+
+Consider reviewing and updating your configuration files with the `--update_config` or `--generate_config` CLI parameters. Review the [toml config quick reference](../snippets/toml-config-commands.md), or the [CLI documentation](../commands/command-line-interface.md#nano_node-commands) for additional details.
+
+### Known Issues
+
+Bootstrapping from scratch with pruning enabled causes the node to crash. As a potential workaround, node operators may be able to bootstrap with pruning disabled, and then enable pruning after bootstrapping is complete. A higher max_pruning_depth may also reduce the frequency of crashes. Pruning is considered experimental, so use it at your own risk - pruning is not currently recommended for important production services.
+
+---
+
+## Official V28 Blog Post
+See [here](https://nano.org/en/blog/v27-denarius-preview--eb8bceac) for the official V28 blog post.
+
+---
+
+## V28 GitHub Milestone
+See [here](https://github.com/nanocurrency/nano-node/milestone/34?closed=1) for the V28 GitHub milestone.
+
+---
+
+--8<-- "current-build-links-main.md"