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.

https://github.com/CryptoLions/MSIG_console_manager/tree/FIO

https://msig.app/fio

I can see if I have some examples on my local machine using these scripts.

Eric Butz, [7/25/2023 10:48 AM]
Some helpful notes for getting this working:

To get it to connect to the local wallet I had to run:

pkill fio-wallet
./fio-wallet --http-server-address=127.0.0.1:8900 &

NOTE! make sure there is a carriage return after the last action in actions_list

Eric Butz, [7/25/2023 10:48 AM]
Some examples that might go into 1_actions_list:

./clio.sh push action fio.fee createfee '{"end_point":"wrap_fio_tokens","type":"0","suf_amount":"2000000000"}' -p fio.fee@active

./clio.sh push action fio.oracle regoracle '{"oracle_actor":"gws1hlwlqhq1","actor":"eosio"}' -p eosio@active

./clio.sh push action fio.address regaddress '{"fio_address": "msig1@fiotestnet", "owner_fio_public_key": "FIO7LHcsCJjhywzAvELwdpZnynbELiua8SFjaXx4hu7Fuy3r8P9FC", "max_fee": 40000000000, "actor": "1sjb4apbznnx", "tpid": ""}' -p 1sjb4apbznnx@active

./clio.sh push action fio.oracle regoracle '{"oracle_actor":"mak1ed5b4k1v","actor":"eosio"}' -p eosio@active
./clio.sh push action fio.oracle regoracle '{"oracle_actor":"jnmwi5vu3hle","actor":"eosio"}' -p eosio@active
./clio.sh push action fio.oracle regoracle '{"oracle_actor":"hkzfdcxe11us","actor":"eosio"}' -p eosio@active

./clio.sh push action eosio unregprod '{"fio_address":"zenblocks@fiotestnet","actor":"eosio","max_fee":5000000000}' -p eosio@active

To create a new account

Eric Butz, [3/3/2022 3:02 PM]
@eluzgin the clio code for creating the new account was incorrect in the file I gave you. Bohdan gave me the correct command and created the newsys.b msig. For future reference, this is correct way to add a new account via msig.

First create the file newaccount_payload.json 

{
   "creator": "eosio",
   "name": "fio.escrow",
   "owner": {
      "threshold": 1,
      "keys": [],
      "accounts": [{
         "permission": {"actor": "eosio", "permission": "active"},
         "weight": 1
      }],
      "waits": []
   },
   "active": {
      "threshold": 1,
      "keys": [],
      "accounts": [{
         "permission": {"actor": "eosio", "permission": "active"},
         "weight": 1
      },
      {
         "permission": {"actor": "fio.escrow", "permission": "eosio.code"},
         "weight": 1
      }],
      "waits": []
   }
}

Eric Butz, [3/3/2022 3:02 PM]
Then use the following clio:

./clio.sh push action -j -s -d eosio newaccount newaccount_payload.json -p eosio@active

Telegram discussion: https://t.me/fiotestnetb/10248

you can always check your msigs with cleos:

./cleos.sh multisig review ...

or check tables using the CryptoLions table query tool

Cleos mSig commands;

/home/ubuntu/fio/3.5.x-dev/bin/clio -u https://api.fiotest.alohaeos.com multisig review nyvrxkxhiyql token.2n.c1

/home/ubuntu/fio/3.5.x-dev/bin/clio -u https://api.fiotest.alohaeos.com multisig approve nyvrxkxhiyql token.2n.c1 '{"actor":"nyvrxkxhiyql","permission":"active"}' 241873769

/home/ubuntu/fio/3.5.x-dev/bin/clio -u https://api.fiotest.alohaeos.com multisig cancel nyvrxkxhiyql fiosys.2n.c1 241873769 nyvrxkxhiyql

/home/ubuntu/fio/3.5.x-dev/bin/clio -u https://api.fiotest.alohaeos.com get table -l -1 eosio.msig nyvrxkxhiyql approvals2

/home/ubuntu/fio/3.5.x-dev/bin/clio -u https://api.fiotest.alohaeos.com get table -l -1 eosio.msig nyvrxkxhiyql approvals2 | grep proposal_name

/home/ubuntu/fio/3.5.x-dev/bin/clio -u https://api.fiotest.alohaeos.com get table -l -1 eosio.msig nyvrxkxhiyql approvals2 | grep proposal_name | grep c1 | wc -l

Fees: Type 0 versus Type 1?
To verify actions; must hit api node that has history turned on

To verify fees; use Postman, create GET action, endpoint: http://fiotestnet.blockpane.com/v1/chain/get_fee, with json body of
{ "end_point": "update_encrypt_key"

}

Some fees require a fio_address, i.e. jasonbourne@fioprotocol

BP Tips

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

FIO App Notes

fio-bundles

Building the DevNet tool

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

As this is a private repo, you will need to be granted access as well as have either a GitHub Personal Access Token or other means of ‘cloning’ the repo. If using an access token, the clone url is as follows:

git clone https://<Personal Access Token>@github.com/dapixio/fio-devnet.git

Refer to git - Clone A Private Repository (Github) - Stack Overflow for guidance.

Once the repo is cloned, cd to the fio-devnet/cmd/devnet and execute the cmd, 'go build'. This will build the devnet executable.

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

Install/Configure/Run pgAdmin4 against RDS

See https://www.pgadmin.org/download/pgadmin-4-apt/ for installation instructions

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.

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.
  1. Private/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.
Install PgAdmin on local linux desktop
Configure as follows;
1. Create a new connection; right-click “Servers” and click Register > Server. If a server group has not been created, do that first, then create a Server underneath that group.
  1. On General tab, set the name of the db server
  2. On Connection tab, set Host, Port (default: 5432), Maintenance database (the actual db), and username
  3. On SSH Tunnel tab,
    1. Oregon Tunnel host: ec2-52-13-131-147.us-west-2.compute.amazonaws.com
    2. Oregon Username: ec2-user
    3. N.Virginia Tunnel host: ec2-3-226-116-124.compute-1.amazonaws.com
    4. N.Virginia Username: ec2-user
2. 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.

Its also possible to use postgresql-client software, e.g. psql. to connect to the db. To do one must use ssh or putty to create a tunnel (much like is done above). See Connect to a PostgreSQL Server via SSH Tunnel - DEV Community for help in doing so.

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, ec2-3-226-116-124.compute-1.amazonaws.com
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
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
Test using a command like; psql --port=5433 --host=localhost --user registration -c "SELECT * FROM public.wallet"

GOLANG

To clean up dependencies, run

Tips & Tricks

Tagging

To tag a branch (or move a tag): https://stackoverflow.com/a/8433371, https://stackoverflow.com/questions/20076233/replace-remote-tag-with-git
To delete a tag, see https://stackoverflow.com/questions/5480258/how-can-i-delete-a-remote-tag to delete a tag
To delete a branch https://stackoverflow.com/questions/2003505/how-do-i-delete-a-git-branch-locally-and-remotely, https://www.baeldung.com/git-delete-branch-locally-remotely
https://git-scm.com/docs/git-tag#_on_re_tagging, https://stackoverflow.com/questions/66913267/wrong-commit-hash-with-git-rev-parse-tag

Tagging workflow

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

Release:
1. Remove tag (both remote and local)
2. Tag with annotated tag (include -a and -m <msg>)

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

Account Information

To get account info run

To compare account info between testnet and localnet, run

Bash-isms

to find files and replace strings

Troubleshooting

Database Dirty Flag

Relevant Issues

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!
Dirty Flag Issue:
1. Ye olde folder deletion problem where you have to manually delete some folders when doing a replay
  1. https://fioprotocol.atlassian.net/browse/BD-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. https://fioprotocol.atlassian.net/browse/BD-1953

Outcome

Thanks Ross; this particular setup has /var/lib/fio/ with data and history folders. It has no snapshots nor blocks directories in the data folder. There were two history* folders.

Taking what you said and doing what I could, I deleted the contents of the two history folders (backed up elsewhere). and restarted.

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

Passcode: @HQdfv5=

Data Integration

Google Sheets to Json:
http://blog.pamelafox.org/2013/06/exporting-google-spreadsheet-as-json.htmlhttps://gist.github.com/florentdescroix/9513cfd957f8b2cde7b832cf7170c84a

Telegram: Telegram Group/Channel Data Extraction (User’s information, chats, and specific messages), and Data Processing | by Dayal Chand Aichara | Game of Data | Medium

FIO macOS build and deploy notes

AWS MacOS Instance: MacOSX Sonoma (14.x)

Instance Type: mac1
Dedicated Host: mac1.metal

Xcode: 11.7

Download and install using; sebsto/xcodeinstall, accept license using sudo xcodebuild -license accept

Downloads - Apple Developer

FIO Repo: fioprotocol/fio, release 3.5.x-dev (release/3.5.x-dev)

Core Chain Development

Miscellaneous

Worker Proposals

Payment Requests

FIO Explorers/Monitors

FIO Tools

mSig Info