Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Worker Proposals

Worker Proposals - Agile board - FIO Issue Tracking (atlassian.net)

Payment Requests

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

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

Jira Legacy
serverSystem JIRAJira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-29

Jira Legacy
serverSystem JIRAJira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-70

Jira Legacy
serverSystem JIRAJira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-125

Jira Legacy
serverSystem JIRAJira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-207


Jira Legacy
serverSystem JIRAJira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-121

FIO-249: [Core Infrastructure] August 2023 - LeetSoft Solutions, LLC

Jira Legacy
serverSystem JIRAJira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-313

Jira Legacy
serverSystem JIRAJira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-376

Jira Legacy
serverSystem JIRAJira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-274

Jira Legacy
serverSystem JIRAJira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-431

FIO Explorers/Monitors

FIO TestNet Network Monitor

FIO MainNet Network Monitor (fioprotocol.io)

FIO Tools (blockpane.com)

EOS Tools and Info - Aloha EOS

FIO MainNet Health

FIO MainNet Block Explorer and Wallet

FIO TestNet Block Explorer and Wallet

FIO Tools

Several tools have been built and are still in use by the FIO Protocol, i.e., cryptonym, devnet, and fiotop.

Blockpane Repo (cryptonym, fiowatch, fiotop)

CryptoLions/MSIG_console_manager

See the following repos for more info;

Cryptonym Notes:

Default config

  • key: FIO6G9pXXM92Gy5eMwNquGULoCj3ZStwPLPdEb9mVXyEHqWN7HSuA

  • max_fee: 23.926127683

  • actor: o2ouxipw2rt4

  • tpid: tpid@blockpane

mSig Info

https://dev.fio.net/docs/command-line-interface

https://dev.fio.net/docs/multisig

Eric Butz, [7/25/2023 10:40 AM]
I used

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-471

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-472

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-505

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-539

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-586

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-635

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-699

FIO-629: Core Infrastructure

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-740

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-789

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-849

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-778

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-937

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-983

FIO mSig Acct Payment Requests

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-482

Jira Legacy
serverSystem Jira
serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
keyFIO-587

FIO Explorers/Monitors

FIO TestNet Network Monitor

FIO MainNet Network Monitor (fioprotocol.io)

FIO Tools (blockpane.com)

EOS Tools and Info - Aloha EOS

FIO MainNet Health

FIO MainNet Block Explorer and Wallet

FIO TestNet Block Explorer and Wallet

FIO Tools

Several tools have been built and are still in use by the FIO Protocol, i.e., cryptonym, devnet, and fiotop.

Blockpane Repo (cryptonym, fiowatch, fiotop)

CryptoLions/MSIG_console_manager

See the following repos for more info;

Cryptonym Notes:

Default config

  • key: FIO6G9pXXM92Gy5eMwNquGULoCj3ZStwPLPdEb9mVXyEHqWN7HSuA

  • max_fee: 23.926127683

  • actor: o2ouxipw2rt4

  • tpid: tpid@blockpane

mSig Info

https://dev.fio.net/docs/command-line-interface

https://dev.fio.net/docs/multisig

Eric Butz, [7/25/2023 10:40 AM]
I used Cryptolion's MSIG tool and it was fairly straightforward. The main complexity is with creating contract updates.

...

  1. Use appropriate pass-through (Bastion) servers with user ec2-user in ssh command

    1. Us-West-2: 52.13.131.147, ec2-52-13-131-147.us-west-2.compute.amazonaws.com

    2. US-East-1: 3.226.116.124, ec2ec2-3-226-116-124.compute-1.amazonaws.com

  2. ssh -L localhost:5433:registration-b-20230614.cibwv8nm92hc.us-east-1.rds.amazonaws.com:5432 ec2-user@ec2-3-226-116-124.compute-1.amazonaws.com -i /home/ubuntu/.ssh/id_rsa.michael-fioprotocol.io

    1. Replace ‘ssh’ above with ‘ssh -o ExitOnForwardFailure=yes -f -N’ to put into background

    2. Repl Prod east: ssh -o ExitOnForwardFailure=yes -f -N -L localhost:5433:registration-b-20230614.cibwv8nm92hc.us-east-1.rds.amazonaws.com:5432 ec2-user@ec2-3-226-116-124.compute-1.amazonaws.com -i /home/ubuntu/.ssh/id_rsa.michael

    -fioprotocol.io
    1. Replace ‘ssh’ above with ‘ssh -o ExitOnForwardFailure=yes -f -N’ to put into background-fioprotocol.io

    2. Repl Prod eastwest: ssh -o ExitOnForwardFailure=yes -f -N -L localhost:5433:registration-b-2023061420230717.cibwv8nm92hccnxphxkusylu.us-eastwest-12.rds.amazonaws.com:5432 ec2-user@ec2-3-226-116-124.compute-1.amazonaws.com -i /home/ubuntu/.ssh/id_rsa.michael-fioprotocol.io

    3. Repl Prod west: ssh -o ExitOnForwardFailure=yes -f -N -L localhost:5433:registration-b-20230717.cnxphxkusylu.us-west-2.rds.amazonaws.com:5432 ec2-user@ec2-52-13-131-147.us-west-2.compute.amazonaws.com -i /home/ubuntu/.ssh/id_rsa.michael-fioprotocol.io

  3. Test using a command like; psql --port=5433 --host=localhost --user registration -c "SELECT * FROM public.wallet"

GOLANG

...

    1. com:5432 ec2-user@ec2-52-13-131-147.us-west-2.compute.amazonaws.com -i /home/ubuntu/.ssh/id_rsa.michael-fioprotocol.io

  1. Test using a command like; psql --port=5433 --host=localhost --user registration -c "SELECT * FROM public.wallet"

GOLANG

Code Block

// 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 specific commit (put in require)
tag
// go get github.com/fioprotocol/fio-go@943a6a787d29go@v1.1.0-rc1
// ==> github.com/fioprotocol/fio-go v1.01.6-0.20230331152418-943a6a787d29rc1

// PointReplace toremote latestdependency (implied)with inlocal branchone
// go getreplace github.com/fioprotocol/fio-go@developgo // ==> github.com/home/ubuntu/repos/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

Code Block
go mod tidy

Tips & Tricks

Tagging

Tagging workflow

  1. Release candidate: tag with lightweight tag (do not include -a)

Code Block
languagebash
git tag v2.9.0
git push origin --tags
  1. Release:

    1. Remove tag (both remote and local)

    2. Tag with annotated tag

Code Block
languagebash
git push origin :refs/tags/v2.9.0-rc1
git tag --delete v2.9.0-rc1
git tag -fa v2.9.0 -m "Version 2.9.0"
git push origin --tags

Account Information

To get account info run

Code Block
languagebash
./clio -u http://127.0.0.1:8889 get account fio.treasury
./clio.sh get account fio.treasury

To compare account info between testnet and localnet, run

Code Block
languagebash
./clio -u http://52.35.164.8:8888 get account fio.treasury
./clio.sh get account fio.treasury

To clean up dependencies, run

Code Block
go mod tidy

Tips & Tricks

Tagging

Tagging workflow

  1. Release candidate: tag with lightweight tag (do not include -a)

Code Block
languagebash
git tag v2.9.0
git push origin --tags
  1. Release:

    1. Remove tag (both remote and local)

    2. Tag with annotated tag (include -a and -m <msg>)

Code Block
git push origin :refs/tags/v2.9.0-rc1
git tag --delete v2.9.0-rc1
git tag -fa v2.9.0 -m "Version 2.9.0"
git push origin --tags
  1. To verify tag

    1. git rev-parse of a tag will show a commit just for the tag. Use git show <commit> to view commit info

Code Block
git rev-parse --verify HEAD
git rev-parse v2.9.0
git rev-parse v2.9.0^{commit}

Account Information

To get account info run

Code Block
languagebash
./clio -u http://127.0.0.1:8889 get account fio.treasury
./clio.sh get account fio.treasury

To compare account info between testnet and localnet, run

Code Block
languagebash
./clio -u http://52.35.164.8:8888 get account fio.treasury
./clio.sh get account fio.treasury

Bash-isms

to find files and replace strings

Code Block
find . -type f \( -exec grep -l "\/home\/ubuntu\/fio\/upgrade" {} \; -false -o -exec sed -i 's/\/home\/ubuntu\/fio\/upgrade/\/home\/ubuntu\/tmp\/fio\/apts/g' {} \; \)
Code Block
find . -type f \( -exec grep -l "fio\/upgrade" {} \; -false -o -exec sed -i 's/\/home\/ubuntu\/fio\/upgrade/\/home\/ubuntu\/tmp\/fio\/apts/g' {} \; \)```

Troubleshooting

Database Dirty Flag

...

  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. Dirty Flag Issue:

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

      1. Jira Legacy
        serverSystem JIRAJira
        serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
        keyBD-1953

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

    2. [Ross/EOSphere} Restart with a snapshot from here and check the nodeos usage example at the bottom.https://snapshots.eosphere.io. Also delete the two history folders in the nodeos binary directory you started from.

    3. Jira Legacy
      serverSystem JIRAJira
      serverId5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
      keyBD-1953

...

All is good with that node now! Repeated on my third node and wallah - Great. Thank you so much.

Dashboard

FIO Dashboard

Dev Hub/Dev Hub Sitebuilder: FIO Protocol Developer Hub / FIO ReadMe / FIO readme.com 1.9 Docs

Zoom Recordings

https://us02web.zoom.us/rec/share/pf3TGOdPVzVYSatz6JpQts0TI88PHZtXlenVVMjCOYjMUN33ZnK7nwdUkWBDTU76.h9ElTfjcib-d0JFU?startTime=1655311884000

...