Skip to content

Instantly share code, notes, and snippets.

@cc32d9
cc32d9 / enterprise_antelope_system_contracts.md
Last active August 23, 2022 08:58
Enterprise Antelope system contract requirements
  1. Permissioned chain with granular permissions for specific actions:
  • account creation
  • contract deployment
  • registering as producer
  1. No voting: the permissioned accounts just regproducer and start producing

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

  3. No system token

@cc32d9
cc32d9 / leap_3.2_build.md
Last active June 27, 2023 20:17
Leap 3.2.x build

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
cc32d9 / atomicdata.hpp.diff
Created June 25, 2022 13:21
atomicdata.hpp adaptation to use in your own contract
--- /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
cc32d9 / eos_mandel_upgrade_survey.md
Created April 13, 2022 15:35
EOS Mandel upgrade survey
  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
cc32d9 / backup_configs.sh
Created October 10, 2021 13:17
backup_configs
#!/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.
##
@cc32d9
cc32d9 / KV_maps_in_EOSIO_discussion.txt
Last active September 29, 2021 07:41
KV maps in EOSIO discussion
From EOSIO Developers Chat: https://t.me/joinchat/0uhWYfXVpPlkNTA1
Jesse - CalEOS.io (caleosblocks), [27.09.21 23:27]
So, KV_DATABASE feature uses disk but when that's activated the current multiindex tables are still in RAM?
Jesse - CalEOS.io (caleosblocks), [27.09.21 23:27]
I thought they went together... both to disk
Todd Fleming, [27.09.21 23:51]
What we created:
@cc32d9
cc32d9 / atomicassets_cleos_example.sh
Created June 5, 2021 08:21
AtomicAssets cleos example
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
cc32d9 / eos_stats.txt
Last active February 5, 2021 09:10
EOS stats 2020-11-12
MariaDB [eosio_activity]> select sum(counter) S, count(distinct authorizer) A, action, contract from eos20210116_DAILY_COUNTS where xday='2021-02-03' group by contract, action order by S desc limit 50;
+-----------+------+--------------+--------------+
| S | A | action | contract |
+-----------+------+--------------+--------------+
| 192012703 | 4878 | transfer | eosio.token |
| 93927965 | 76 | transfer | eidosonecoin |
| 1972506 | 24 | transfer | eosiopowcoin |
| 762427 | 26 | mine | gravyhftdefi |
| 482590 | 4 | stamp | wordproofcom |
| 416986 | 1 | quietransfer | gravyhftdefi |
@cc32d9
cc32d9 / Aarin_Hagerty_on_history_of_DPOS_governance.md
Created October 31, 2020 09:22
Aarin Hagerty on history of DPOS governance

https://t.me/EOSproject/1561416

Aarin Hagerty, [30.10.20 14:48] [In reply to Luka Perrrcic] I would like to provide some historical context regarding this discussion of DPoS voting mechanisms.

BitShares ended up with an approval voting system (which one can think of as 1 token infinity votes) for voting for BP (block producer) candidates which then ranked them by approval vote and selected the top N as the set of active block producers. I don't remember the exact series of events and reasoning that led to that decision, but I am sure most of it can be found on the old BitSharesTalk forum (e.g. https://bitsharestalk.org/index.php?topic=5205.0).

There are some advantages of an approval voting system over cumulative voting (https://en.wikipedia.org/wiki/Cumulative_voting), which one can basically think of as 1 token 1 divisible vote, particularly in the case of single winner elections. For example it passes the favorite betrayal criterion (https://electowiki.org/wiki/Favorite_betrayal_criterion) whereas cu

@cc32d9
cc32d9 / EOSIO_public_node_DOS_protectrion.sh
Last active September 2, 2022 20:35
EOSIO public node DOS protectrion
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