---
# System prepended metadata

title: Scotbot Dual Chain

---

# Scotbot Dual Chain

## Properties
Properties of how it will work:

1. Hive chain will be crawled in parallel, and will process posts votes in a parallel storage. Accounts will be mirrored with separate voting power from Steem, and stake balances will be taken from the steem account. 
   - Tribes must opt in to this.
   - **Note that there will be independent mana bars for Steem / Hive. This in essence will double everyone's effective voting ability. This is a technical limitation to the implementation.**
   - If you set vote multipliers, for the time being it is only Steem side.
   - Following authors must be done Steem side (for now). Reblog does not work yet.
   - Promotion ops must be done Steem side. If it is a hive-based post, the permlink needs a prefix, like `h@author/permlink`.
   - A post created from Steem must be voted / commented on Steem. A post created from Hive must be voted / commented from Hive.
2. The timing of when Hive ops are indexed is not predictable, as it is done entirely in parallel. So it can be ahead or behind of the Steem indexing. Meaning, if Steem side is behind, the stake backing your voting power on Hive posts will reflect a slightly-behind state.
3. All token operations must still be done on the Steem chain while Steem Engine is not migrated to Hive.
   In particular, note that new hive accounts that are not on Steem cannot have stake (but they can be delegated to). And they cannot actually claim rewards due to not having a Steem Engine account.
4. API will not be prefixing anything. It will expose endpoints like `/@author?hive=1`,  `/@author/permlink?hive=1`, and feeds will stream both types, and there will be a `hive` boolean to indicate if the content should be fetched from a Hive node.
5. Pending payouts for hive and steem are separated. (hive vs not-hive account lookup in point (4))


## In Progress:

* Option to disable crawling the Steem post/vote ops, which may be important given the double-voting-bar implementation.
* Auto-Claim for hive based posts. This will likely need to be audited first to make sure it is functioning as expected, but the rewards distribution has already been tested locally.
* Nitrous interface changes are still in the works. For now we can enable crawling for opted in tribes.
  - Follow and reblogging from Hive ops. 
  - Follower feeds may not include hive posts yet.
* Vote multiplier from hive ops.
* Tribe mute from hive ops. (can still be done on steem side using `h@` prefix)
