Author Topic: A Definitive Guide to Nodes, Wallets, and Keys: Types and Terminology  (Read 755 times)

0 Members and 1 Guest are viewing this topic.

Offline litepresence

I am not an expert here, I'm simply an algo trader looking to integrate to the Bishares DEX environment by connecting to existing node architecture - without running my own node.  I have asked a lot of questions lately to Node Admins and have concluded there is a good deal of terminology involved that needs clarification.   There are also risks when dealing with existing nodes, that need to be mitigated.  So, please if you are an expert, chime in and I'll update this OP to summarize key points.   

This OP was initial populated with cut/paste commentary via Node Admin channel on Telegram.


NODES


some universal truisms:

- nodes are in no way uniform
- however, all nodes store all blocks
- any node can go rogue at any time
- every node is a man-in-the-middle between you and the blockchain


A node can be:

P2P

RPC

API - exposed to a network, either LAN or WAN

FULL -  nodes which provide full histories;  nodes which provide full histories; needs several tens of gigs of RAM; x5670 with 100G ram should be good for full history node

SEED - full nodes with publicly reachable p2p port

WITNESS - is a matter of votes, but you can run a witness node wich locally validates the blocks

PRODUCTION

LOAD BALANCED

PUBLIC

DOCKER

PAID

DELAY NODE

OWN USE

BLOCK PRODUCING

WHITE LISTED

BLACK LISTED

ACTIVE

STANDBY

LOW LATENCY

UNRESPONSIVE

TESTNET - testnet is actually used to determine if it's mainnet or testnet

SYNCHRONIZED

DATACENTER

HARDENED

SSL

VPS

DELAYED

INITIAL

FAKE - fake.automatic-selection is a hard-coded psuedo server

BITSHARES OFFICIAL - deployed with bitshares UI

CRYPTOBRIDGE OFFICIAL - deployed with cryptobridge UI

UP TO DATE - has a head block that is less than 3 seconds old

STALE - has a head block that is greater than 3 seconds old

PROPERLY DEPLOYED

LATEST VERSION

VERSION 171105a - if there are many wicks in price chart, it's on this version

pre-VERSION 1802xx - if owner key signature is not able to change active permissions, it's before 1802xx

ROGUE - a node can delay, refuse, or reorder your buy/sell/cancel or other requests.   A rogue node can also return inaccurate information to all or any one individual.  A rogue node can NOT modify or create a buy/sell/cancel operation on your behalf.  A rogue node can provide false account ID in an attempt to get you to send funds to bad address.


WORKING

VERIFIED



WALLETS


CLI - command line interface
PYBITSHARES
LIGHT
WEB WALLET
FAUCET - a pool of funds used to pay the registration fee for the new accounts, there are currently several public faucets up



PASSWORDS and KEYS


BRAIN

PASSPHRASE