for i in $(curl -s --url "http://127.0.0.1:7776/" --data "{\"agent\":\"dpow\",\"method\":\"ipaddrs\"}" | jq -r '.[]') ; do ping -c 3 $i | grep time | awk '{print $4 $7}' | sed 's/:time=/,/' | grep -v packet; done
195.154.79.11,288
195.154.79.11,287
195.154.79.11,287
148.251.9.12,298
148.251.9.12,298
148.251.9.12,298
Captain Mylo imylomylo
curl -s --user $rpcuser:$rpcpassword --data-binary '{"jsonrpc": "1.0", "id": "curltest", "method": "tokenaddress", "params": []}' -H 'content-type: text/plain;' http://127.0.0.1:$rpcport/ | jq -r '.result'
{
"result": "success",
"TokensCCAddress": "RAMvUfoyURBRxAdVeTMHxn3giJZCFWeha2",
"TokensCCBalance": 0.0001,
"TokensNormalAddress": "RCNgAngYAdrfzujYyPgfbjCGNVQZzCgTad",
"TokensNormalBalance": 0,
"myCCAddress(Tokens)": "RBjnhNaqtSGym1PqpaQL3jY3XHgpH9qTRK",
"myCCbalance(Tokens)": 5,
##
T 127.0.0.1:44346 -> 127.0.0.1:7777 [AP] #1254
POST /http://127.0.0.1:12277 HTTP/1.1.
Host: 127.0.0.1:7777.
Connection: keep-alive.
Content-Length: 68.
Authorization: Basic dXNlcjE3MTc3NTU4NTE6cGFzczczOGQ2ODMxOTZhNGI0YzNhYWFlMTE4ZTg1ZTNmZTljZjRiNDA3NDc5MzNhMzJjZWY1OGNiOWIzNTcyN2E5ZjQ5MA==.
Origin: http://localhost:8080.
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36.
####
T 127.0.0.1:44282 -> 127.0.0.1:7777 [AP] #1194
OPTIONS /http://127.0.0.1:12277 HTTP/1.1.
Host: 127.0.0.1:7777.
Connection: keep-alive.
Access-Control-Request-Method: POST.
Origin: http://localhost:8080.
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36.
DNT: 1.
imylomylo
/ trace.getinfo.rpc.md
Created
May 12, 2019 06:05
network trace getinfo RPC from browser with cors anywhere
mylo@swift:~/cors-anywhere$ sudo ngrep -d any -W byline port 7777
[sudo] password for mylo:
interface: any
filter: ( port 7777 ) and (ip || ip6)
####
T 127.0.0.1:44942 -> 127.0.0.1:7777 [AP] #4
OPTIONS /http://127.0.0.1:12277 HTTP/1.1.
Host: 127.0.0.1:7777.
Connection: keep-alive.
there are way too many dependencies installed on the first line, because this was just taken from another system for building asterisk voip servers in 2012.
1 yum install -y epel-release unixODBC unixODBC-devel libtool-ltdl libtool-ltdl-devel mysql-connector-odbc ntp wget flex gcc gcc-c++ make kernel-devel kernel-headers libtiff libtiff-devel libxml2 libxml2-devel lynx ncurses ncurses-devel newt newt-devel openssl-devel pam-devel perl-DBD-MySQL perl-DBI screen sox speex-devel tftp-server zlib zlib-devel curl libcurl-devel sqlite sqlite-devel
2 git
3 yum install -y git
4 git clone https://github.com/komodoplatform/komodo
5 cd komodo/
6 ./zcutil/fetch-params.sh
7 ./zcutil/build.sh
8 apt-get install -y zip
imylomylo
/ Verus-Komodo-Fintech.md
Created
April 30, 2019 12:15
Verus & Komodo Fintech: Onchain pegs & stablecoins
Mike's response to jl777s comments about pegs and stablecoins on-chain:
miketout04/20/2019
@jl777c is right that we don't have price feeds or pegs yet. We do support CCs, but before adding these features, I want to make sure that we really understand as much of the implications in all cases as possible for all parts of the PBaaS ecosystem, and if we do it in the Verus community, rather than someone's independent PBaaS project, that it's well considered, especially relative to the reserve currency support we will have. I'm not saying that it won't be the right thing, just that I haven't worked through the edge cases for myself mathematically yet. For example, if across the system of chains, there would be a way to generate price fluctuations and slowly earn money by arbitraging through synthetic price discrepancies, I'd consider that a leak in the value that could be exploited and would want to consider what it might motivate if/when someone figured it out. Also, if there could be some susceptibility, due
miketout04/19/2019
I think we should be able to bring up a test chain for people to try merge mining when I coordinate with @0x03 about nodes. We will all be able to mine, stake, and make various chains that we merge mine and stake together. There is still a fair amount of work to do before a mainnet release, but it's pretty cool to just load up chains that you've never seen by name and then be able to merge mine a number of chains automatically. each chain runs with its own daemon, and as long as Verus or VerusTest is loaded, they will autorecognize each other, notarize, and merge mine through VRSC or VRSCTEST. Of course, you can configure custom network setups by editing the .conf file to merge mine daemons on different machines, but the default is simple as well. When a daemon goes down, it simply stops merge mining, but all the others continue. If the VRSC or VRSCTEST daemons are stopped, other mining daemons start mining solo. This user experience work took a lot of thought, design, and significant c
imylomylo
/ Verus-Wallet-PBaaS.md
Created
April 30, 2019 12:07
Verus Wallet Using PBaaS for Discovery & Exchange
In response to a new wallet and it's functionality with PBaaS:
miketout04/16/2019
PBaaS is not something that you'll probably see first as a new wallet, as we'll be testing across the community for a little while. It's actually a scalable system of coordinated blockchains with Verus at the core. Right now, I'm running one PBaaS chain, and merge mining, as I wait until its start block. You can now define chains, start chains, connect to either Verus or the test network to get all the information about available PBaaS chains, and start them up based only on a connection to Verus. After the chain has been loaded once from Verus, or if you were able to get the parameters another way, such as a simple install or config file, you can then load the PBaaS chain anytime, whether Verus is running or not. All PBaaS chains can mine independently, similar to how any chain does today, or if you either just run them on the same PC or on multiple PCs that point to each other, they will recognize when different chains co