Below is a full manual recreation of everything the script selfsteal.sh does, but executed by hand on a clean Ubuntu/Debian server.
Follow every block in order – nothing is left out.
# – run as root$ – run as normal user (rarely used here)# inside code blocks are comments – read but do NOT type the #
| peers="cdb11cf19cce0ca6da57a067df86c19b794fcf2b@union-rpc.systemd.run:26656"; \ | |
| sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$peers\"/" $HOME/.union/config/config.toml | |
| SNAP_RPC="https://union-rpc.systemd.run:443"; \ | |
| LATEST_HEIGHT=$(curl -s $SNAP_RPC/block | jq -r .result.block.header.height); \ | |
| BLOCK_HEIGHT=$((LATEST_HEIGHT - 1000)); \ | |
| TRUST_HASH=$(curl -s "$SNAP_RPC/block?height=$BLOCK_HEIGHT" | jq -r .result.block_id.hash); \ | |
| echo $LATEST_HEIGHT $BLOCK_HEIGHT $TRUST_HASH | |
| sed -i -E "s|^(enable[[:space:]]+=[[:space:]]+).*$|\1true| ; \ |
| сделай краткое изложение этого твита | |
| https://twitter.com/NEARProtocol/status/1722276234946826691 | |
| The NEAR Foundation and | |
| @0xPolygonLabs | |
| are set to deliver the future of zero-knowledge for WASM based blockchains with zkWASM. | |
| - | |
| Empowering greater security, scalability, developer flexibility, and interoperability in the open web🌐 | |
| - |
| rm -f out | |
| mkfifo out | |
| trap "rm -f out" EXIT | |
| while true | |
| do | |
| cat out | nc -w1 -l 1500 > >( # parse the netcat output, to build the answer redirected to the pipe "out". | |
| export REQUEST= | |
| while read line | |
| do | |
| line=$(echo "$line" | tr -d '[\r\n]') |
| # get speedometer | |
| apt install speedometer | |
| # get external interface name | |
| IF="$(route | grep '^default' | grep -o '[^ ]*$')" | |
| # start speedometer | |
| speedometer -t $IF -r $IF |
| { | |
| "annotations": { | |
| "list": [ | |
| { | |
| "builtIn": 1, | |
| "datasource": "-- Grafana --", | |
| "enable": true, | |
| "hide": true, | |
| "iconColor": "rgba(0, 211, 255, 1)", | |
| "name": "Annotations & Alerts", |
This example is specifically for my Osmosis seed node, that I run in the cloud, all my other nodes are on hardware, and I use a very different setup on those.
These instructions should work on just about any cloud provider, by striping block devices it's possible to get much higher IOPS and throughput. On Omosis in particular this is important. It doesn't cost any more to use striped volumes, so for example 3 40GB volumes cost the same as a single 120GB, but give (almost) 3x the performance.
After provisioning new block devices (do not format automatically) in the DO console and attaching them, ssh into the droplet and as root follow the directions below. I try to shoot for < 50% usage, so right now with about 120GiB needed, three 90GB volumes will do nicely.
_Note that extending the volume group in the future will require adding exactly the same number and size of volumes. Alternatively you can just use the same procedure here to move the files into a new vol
| #!/bin/bash | |
| ### This is an example script that sets up IP tables with Docker. Many admins are not aware that UFW | |
| ### and Docker do not play well together, and accidently expose RPC ports and vulnerable services to | |
| ### the network. This replaces UFW with Netfilter-persistent and adds rules to the DOCKER-USER chain | |
| ### which is the correct way to filter incoming traffic with docker. This specific example is for a | |
| ### Tendermint node running via docker, and wireguard / ssh running directly on the host. | |
| # CHANGE THIS TO ACTUAL PUBLIC INTERFACE!!!!!!!!!! |
Setup:
simd tx distribution set-withdraw-addr <claim_address> -y --from validator
simd tx authz grant <claim_address> generic --msg-type=/cosmos.distribution.v1beta1.MsgWithdrawValidatorCommission --from validator
simd tx authz grant <claim_address> generic --msg-type=/cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward --from validator
I hereby claim:
To claim this, I am signing this object: