cc32d9

apt-get update && apt-get install -y aptitude git lxc-utils zfsutils-linux netfilter-persistent sysstat 

# find the partition ID that is linked to the storage serial number. 
# This will prevent from losing the partition if disk mapping changes
ls -l /dev/disk/by-id/ | grep sda6
zpool create -f zdata /dev/disk/by-id/wwn-0x600507604092b628236df4851535cef5-part6

## Fixate internal IP address of the container
systemctl stop lxc-net
sed -i -e 's,^.*LXC_DHCP_CONFILE,LXC_DHCP_CONFILE,' /etc/default/lxc-net

cc32d9

Building Antelope.IO Leap 3.2.x

The procedure is tested on Ubuntu 20.04 and 22.04.

As a result, binary packages will be placed in build/ subfolder of where you cloned the Git repository (e.g. leap-3.2.3wax01-rc4-ubuntu22.04-x86_64.deb).

If you need to install the binaries in a specific separate directlry (for example, if several different versions of nodeos need to run on the same server), unpack the debian package as follows:

cc32d9

alias wtcleos='cleos -v -u https://testnet.wax.pink.gg'
cleos wallet unlock -n testnet

wtcleos push action atomicassets createcol '["cc32dninenft", "loremipsumdo", true, [], [], 0.05, []]' -p cc32dninenft

wtcleos push action atomicassets addcolauth '["loremipsumdo", "cc32dninenft"]' -p cc32dninenft

wtcleos push action atomicassets createschema '["cc32dninenft", "loremipsumdo", "tempor", 
[{"name":"name", "type":"string"}, {"name":"commodo", "type":"string"}, {"name":"consequat", "type":"uint32"}, {"name":"ullamco", "type":"float"}]]' -p cc32dninenft

cc32d9

apt install iptables-persistent

cat >/usr/share/netfilter-persistent/plugins.d/ddos <<'EOT'
#!/bin/sh
case $1 in

    start)
iptables -N eosio-api
iptables -N eosio-apisyn
iptables -N eosio-p2p

cc32d9

1. Permissioned chain with granular permissions for specific actions:

• account creation
• contract deployment
• registering as producer

2. No voting: the permissioned accounts just regproducer and start producing

3. No RAM or CPU purchasing: unlimited quotas for all accounts

4. No system token

cc32d9

1. What's your project/dapp name? (free-form)

2. Please describe shortly how EOS APIs are used in your project.

3. Do you host your own EOS nodes?

   • Yes
   • No

4. What type(s) of API do you require? (multiple choice)

• Chain API (push transactions, query tables)

cc32d9

--- /home/cc32d9/tmp/atomicassets-contract/include/atomicdata.hpp       2021-03-20 12:34:39.833672293 +0100
+++ atomicdata.hpp      2022-05-04 12:06:12.048674881 +0200
@@ -6,7 +6,7 @@
 using namespace eosio;
 using namespace std;
 
-namespace atomicdata {
+namespace atomicassets {
 
     //Custom vector types need to be defined because otherwise a bug in the ABI serialization

cc32d9

How EOSIO nodeos writes snapshots

EOSIO commit c6a7ec0dd816f98a6840f59dca9fed04efd9f7a5 (v2.0.6).

plugins/producer_plugin/producer_plugin.cpp line 1156: producer_plugin::create_snapshot is called by HTTP API call.

plugins/producer_plugin/producer_plugin.cpp line 1187: opens the output stream,

cc32d9

@SirFuzzalot presented an idea for a new PB pay model for an EOSIO network in https://t.me/EOSPros

Fuzzy, [12.05.19 04:56]
Here is my thought on fixing dpos away from pageantry though. 
Let me find the discussion (should prob post it on whaleshares first but oh well)

Fuzzy, [12.05.19 05:03]
Ok ill just type it here since i am no longer in the group i posted it in initially.

cc32d9

#!/bin/sh

## This simple script is copying configuration files and directories
## from your server to your private Git repository. make sure that the
## Git repository is private and under your control.
##
## Put your directory and file names into /etc/backup_configs and run
## the script. It will create a local Git working directory, copy
## files into it, and push the update to your Git repository.
##