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

...

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)

FIO Explorers/Monitors

FIO TestNet Network Monitor

...

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.

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.

      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.

2. Install PgAdmin on local linux desktop

3. Configure as follows;

   1. Address Bastion OregonCreate 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

      User Bastion

      1. 1. Oregon Username: ec2-user

      Address Bastion

      1. 1. N.Virginia Tunnel host: ec2-3-226-116-124.compute-1.amazonaws.com

      User Bastion

      1. 1. 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.

   3. 

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.

1. 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

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

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

...