Difference between revisions of "Altchain vBFI Preview"
VeriBlockTim (talk | contribs) (→Links) |
VeriBlockTim (talk | contribs) |
||
| Line 2: | Line 2: | ||
See: https://veriblock.org/vbfi | See: https://veriblock.org/vbfi | ||
| + | |||
| + | '''This beta has not officially shipped, there will be bugs.''' | ||
__TOC__ | __TOC__ | ||
| Line 9: | Line 11: | ||
This is a preview of Altchain vBFI (sometimes referred to in developer shorthand as "ABFI"), | This is a preview of Altchain vBFI (sometimes referred to in developer shorthand as "ABFI"), | ||
| − | |||
| − | |||
== Links == | == Links == | ||
Revision as of 21:08, 4 November 2021
See: BTCSQ, How_VeriBlock_PoP_vBFI_Protects_Altchains
See: https://veriblock.org/vbfi
This beta has not officially shipped, there will be bugs.
Contents
Overview
This is a preview of Altchain vBFI (sometimes referred to in developer shorthand as "ABFI"),
Links
There is vBFI applies to VeriBlock NodeCore network itself, and Altchain vBFI applies to an altchain network (such as BTCSQ). Each pop-secured altchain would have its own ABFI monitoring.
There is (1) an API and (2) web visualization.
Eventually this will be included in the explorer, but for now this is a one-off branch.
ABFI
- API
- Web -> http://178.63.228.212:9095/abfi/BTCSQ
vBFI
- API
- Web -> https://vbfi.veriblock.org/ (or http://178.63.228.212:9095/bfi)
For the UI visual, a fork would show up in red, similar to here: How_VeriBlock_PoP_vBFI_Protects_Altchains#vBFI_Example.
The ABFI and vBFI controls are very similar - both have a SP (Security Providing) and SI (Security Inheriting) chain.
