This document captures random notes. This might include troubleshooting, workarounds, or other information that not captured anywhere else.

Payments

[DAO-1665] [Core Chain] LeetSoft Solutions, LLC - Apr 2023 Payment (USDC)

[DAO-1666] [Core Chain] LeetSoft Solutions, LLC - Apr 2023 Payment (Liquid FIO)

FIO Explorers/Monitors

FIO TestNet Network Monitor

...

• blockpane/cryptonym: A FIO Protocol wallet for developers (github.com)

• dapixio/fio-devnet: devnet remote node management tool (github.com)

• fio-tools/fio-top at master · blockpane/fio-tools (github.com)

Cryptonym Notes:

Default config

• key: FIO6G9pXXM92Gy5eMwNquGULoCj3ZStwPLPdEb9mVXyEHqWN7HSuA

• max_fee: 23.926127683

• actor: o2ouxipw2rt4

• tpid: tpid@blockpane

BP Tips

FIO | Sw/eden APT (eosswedenorg.github.io)

FIO App Notes

fio-bundles

#!/bin/bash

# Cmd line arg Usage
#go run cmd/bundles/main.go -d "postgres://registration:O40pWHb40mmdcNbNPUGtg2aIh3qSUX@reg-uat.cluster-cnxphxkusylu.us-west-2.rds.amazonaws.com:5432/registration" -k  "5JrWpJtuPyeXuFzhsAWYSyiT2gCZMR1d8ZdMPFhMkrkYE5NTvn7" -u "https://fiotestnet.blockpane.com" -v

# ENV parameter usage
export DB="postgres://registration:O40pWHb40mmdcNbNPUGtg2aIh3qSUX@reg-uat.cluster-cnxphxkusylu.us-west-2.rds.amazonaws.com:5432/registration"
export NODEOS_API_URL="https://fiotestnet.blockpane.com"
export WIF="5JrWpJtuPyeXuFzhsAWYSyiT2gCZMR1d8ZdMPFhMkrkYE5NTvn7"
go run cmd/bundles/main.go -v

Building the DevNet tool

Clone the dapixio DevNet repo located at dapixio/fio-devnet: devnet remote node management tool (github.com).

...

These steps were performed on a machine with all the necessary dependencies, i.e. go, c/c++ compiler.

Configuring/Running pgAdmin4 against RDS

Access to the RDS is via a bridge, i.e. the Bastion instances are the bridge for access to the registration databases. See https://aws.amazon.com/blogs/database/accessing-an-amazon-rds-instance-remotely-using-aws-client-vpn/ for overview.

1. Contact DevOps group and request access to the RDS instances

   1. Provide specific instance names

   2. For registration databases, access is via Bastion instances mentioned above. In my case I provided SSH public key to DevOps, which was inserted directly on Bastion instance. Provide key via private channel.

   3. Public key may be generated via ssh-keygen, MobaKeyGen, puttygen and is found in ~/.ssh/id_rsa.pub. Note that during keygen no password is needed.

2. Install PgAdmin on local linux desktop

3. Configure as follows;

   1. Address Bastion Oregon: ec2-52-13-131-147.us-west-2.compute.amazonaws.com

   2. User Bastion Oregon: ec2-user

   3. Address Bastion N.Virginia: ec2-3-226-116-124.compute-1.amazonaws.com

   4. User Bastion N.Virginia: ec2-user

   5. Now just configure a connection in PgAdmin with the database credentials, and in the SSH Tunnel tab, pass the bastion instance information according to the region you want to connect to the database.

   6. Image Added

GOLANG

// Point to specific commit (put in require)
// go get github.com/fioprotocol/fio-go@943a6a787d29
// ==> github.com/fioprotocol/fio-go v1.0.6-0.20230331152418-943a6a787d29

// Point to latest (implied) in branch
// go get github.com/fioprotocol/fio-go@develop
// ==> github.com/fioprotocol/fio-go v1.1.0-rc1

// Point to branch with slashes (see bugs 32955, 38861)
// GOPROXY=direct go get github.com/fioprotocol/fio-go@release/v1.1.x

// Point to tag
// go get github.com/fioprotocol/fio-go@v1.1.0-rc1
// ==> github.com/fioprotocol/fio-go v1.1.0-rc1

// Replace remote dependency with local one
//replace github.com/fioprotocol/fio-go => /home/ubuntu/repos/fioprotocol/fio-go

To clean up dependencies, run

go mod tidy

Troubleshooting

Database Dirty Flag

Relevant Issues

1. V1 History config:

   1. https://developers.fioprotocol.io/docs/chain/node-build-history

   2. warning Without the history-index-state-db-size-mb and history-state-db-size-mb settings nodes may stop with the warning: Database has reached an unsafe level of usage, shutting down to avoid corrupting the database. Please increase the value set for chain-state-db-size-mb and restart the process!

2. Ye olde folder deletion problem where you have to manually delete some folders when doing a replay

   1. Jira Legacy
      server System JIRA serverId 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d key BD-1953

   2. To solve this you have to delete the history and history-state folders if you are not running v1 history

BP Input

[Ross/EOSphere} Restart with a snapshot from here and check the nodeos usage example at the bottom.

...