cc32d9

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

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

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

#!/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

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

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

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

{
  "block_num": "283897307",
  "block_timestamp": "2024-10-22T17:37:22.000",
  "trace": {
    "id": "3cb7280487b7dc350f6b1f5acbed43f6692d4d269c47bf5f39c5de7507cea557",
    "status": "executed",
    "cpu_usage_us": "612",
    "net_usage_words": "14",
    "elapsed": "0",
    "net_usage": "112",