Signature for spyked's Keccak regrind of logbot_command_router_python_genesis

April 2nd, 2019

I have read and tested spyked's Keccak regrind of logbot_command_router_python_genesis.

Below is my signature for the Keccak version of logbot_command_router_python_genesis.vpatch
















A bridge to Cuntoo: for the Lenovo x61 (x86_64)

February 25th, 2019

For additional Cuntoo baking documentation, see:

The following is my collected notes on my journey to a bootable Cuntoo usb drive for use with the Lenovo x61. This was a 'clean slate' restart from my previous (failed) attempt, as this time around I installed a heathen, hand-rolled Gentoo on the Lenovo first, then used the Lenovo to install Cuntoo to a usb drive, then booted the Lenovo from the usb drive.

Before I get into the details, here's the vpatch produced1 and kernel config2 used:



Step 0: For the love of Christ, remember to use Screen. (or at least some kind of sane logging)

On my first run-through, I had the great gall to forgo typing "screen -L" before starting my adventures. While obvious to most, it is something that no one ever wished they didn't do.

Step 1: Install the heathen Gentoo

I used a Gentoo "LiveUSB"3 and a recent stage3 tarball4 from, then proceeded to follow the Gentoo handbook:

This was my first successful Gentoo install, so it took me about 2 weeks of reading that handbook5 and troubleshooting various woes, but eventually I got it. For the more seasoned Gentoo-ists in the audience, this will probably be the easier part.

Step 2: Get your Republican toolbox in order (on the Gentoo bridge):

Make sure you have the proper gcc and gnupg versions

I had applied asciilifeform's battle-tested crapolade masks to  /etc/portage/package.mask, but I must've forgotten something because after Gentoo installed I found that I still needed to roll my gcc and gpg versions back.

First, I had to set a  /etc/portage/package.unmask on:


Then emerged gcc:

emerge -a =gcc-4.9.4

This took roughly 2 hours or so, afterwards:

gcc-config 1


Apparently, the portage I ended up with6 required at least gnupg 2.2.4, so I had to roll my portage back to 2.3.8 so it'd play nice with gnupg-1.4.21:

emerge -a =sys-apps/portage-2.3.8

emerge -a =app-crypt/gnupg-1.4.21

Install musl

This was pretty straightforward, and most of what I needed was in the faq For reference, the release I used was From the horse's mouth:

How do I build musl?

In short, simply run ./configure and make. By default make install installs to /usr/local/musl. You may override this by passing --prefix to configure...

...For further details, see the INSTALL file provided with the source distribution.

Note: after installing, remember to add it to your PATH, e.g.:

export PATH=$PATH:/usr/local/musl/bin

You can test that you added it by issuing something like the following:

musl-gcc -v

Install Adacore GNAT 2016

In order to build ave1's GNAT later, you need Adacore GNAT 2016 first.

Head to, filter on "x86 GNU Linux (64 bits)" and for the year choose "2016". Grab the tar, and the README.txt. Read and follow the latter.


SHA-1: 18da74a0ac9df2753bfd9b3d2dcad6e3379825c2


SHA-1: 845147a8c6ef6af29a68144d6b3d228fd226268e

Like with the musl install, remember to add the directory gnat was installed in7 to your PATH. Issue something like "gnatmake -v" to verify

Build ave1's GNAT:

Head to and follow the excellent README.

Note: As always.. PATH! However, this time, make sure your heathen GNAT is no longer in your path and ave1's is.

Get a V setup going that calls out to phf's vtools:

You will need a V that uses phf's keccak-ized vtools. hanbot covers this topic pretty thoroughly in her notes (linked at the top), so I won't rehash too much.

For me, I ended up going with diana_coman's setup outlined in, and it is working splendidly.

Step 3: Cuntoo

This is amply documented at this point, both on and the other guides, so I see no need for a step-by-step.

However, I did hit the following rock using my initial kernel config. The following spew erupted in the middle of building the kernel8:

error reading elf file init/calibrate.o

make[1]: *** [scripts/ init/calibrate.o] Error 1

make[1]: *** Waiting for unfinished jobs....

GEN     usr/initramfs_data.cpio.gz

AS      usr/initramfs_data.o

elf_getdata: No error information

error reading elf file usr/initramfs_data.o

.... [and so on for a dozen or so more files] ...

Now, I have not confirmed 100% this was what my issue actually was, but I ran across the following bug report in the wild that described symptoms that were similar to mine:

Apparently there's a kernel option called CONFIG_STACK_VALIDATION that does some checks at compile time, analyzing all the .o files and validating the metadata. It is also supposed to be disabled by default, but I somehow managed to enable it. And according to the bug report:

These are caused by circular dependencies. The %.o pattern rules in
scripts/ have the stackvalidate binary listed as a
dependency. But stackvalidate gets built *after* archprepare and
scripts/mod, both of which build objects using the %.o pattern rules.

So, it looks like scripts/ tries to look for stackvalidate before it is built, causing some barf.

Anyways, disabling CONFIG_STACK_VALIDATION by setting it to "blank" did the trick for me9. Kernel built without issue.

...and that was it! After my kernel config woes were out of the way, the rest went smoothly. The Lenovo booted into Cuntoo from the usb stick and I was able to login with the user/pass I had set.

  1. sadly, sig did not verify []
  2. generated via 'make menuconfig' []
  3. install-amd64-minimal-20190115T214502Z.iso []
  4. specifically: stage3-amd64-20190122T214501Z.tar.xz []
  5. indeed, I made sure it was word by fucking word []
  6. 2.3.51-r1 []
  7. for me, this was '/usr/gnat/bin' []
  8. If you're using the handy "", the lower-level "" contains the call to "make all'" []

Anglotardation in an Object Oriented World

February 23rd, 2019

While slowly working through my very rough draft of Why TMSR and mulling over what loglines to include, the following jumped into my head (thankfully, I found it):

mircea_popescu: there's nothing BEYOND the world. the things claimed to be so are always and without exception ~inferior~ not superior in the tree of things. one's fantasies of self-realisation, be they wet dreams about little miss rottencrotch two chairs down in chem class or "the rapture", are just so much teenage wank.

god is ~just another trope~. like "the voyage", like "the teenage witch", like "vampires" or "magic horses" or "the island of buyan", god is just another trope. tropes are common places of fiction. fiction is a product of imagination. imagination is mildly-restrained psychogenic noise, which is a class of noise, like wetware thought or like fg output. which are phenomena, which is one half of the world (the other half being objects).

The bolded bits, especially, are what stuck in my mind, and it makes sense to me: We exist in the world as objects (with other objects that don't necessarily belong to the "we" set), and the interaction between them is the phenomena. This simple classification put much into focus, and honestly I wish I heard that in kindergarten instead of the mandatory day of "lets sit in chairs and pretend we're flying to Disneyland" (literally, they did this)

This logline of thought eventually led me back to my copy of "Kritik der reinen Vernunft" von Kant. I've been very slowly chewing through that thing, and each sentence probably takes me good 30 minutes to really grok because I cross-reference each translated word, trying to make sure I'm actually getting the correct meaning. The point being: It takes time, but at the end of it I can actually understand (I think) what the original author means.

Now, up to this point I had prevented myself from even taking a glimpse at an English copy because I've read in the logs how often the English translations are shit. Just for kicks, I finally looked at the one tiny portion of the gutenberg English translation that I had also translated from the original. Let's compare!

First, the original:

I. Von dem Unterschiede der reinen und empirischen Erkenntnis

Daß alle unsere Erkenntnis mit der Erfahrung anfange, daran ist gar kein Zweifel;

denn wodurch sollte das Erkenntnisvermögen sonst zur Ausübung erweckt werden, geschähe es nicht durch Gegenstände,

die unsere Sinne rühren und teils von selbst Vorstellungen bewirken,

teils unsere Verstandestätigkeit in Bewegung bringen, diese zu vergleichen,

sie zu verknüpfen oder zu trennen,

und so den rohen Stoff sinnlicher Eindrücke zu einer Erkenntnis der Gegenstände zu verarbeiten,

die Erfahrung heißt?

Now, my attempt at translating to my mother tongue:

I. Regarding the distinction between pure and empirical knowledge

That all of human knowledge begins with experience, towards this there can be absolutely no doubt;

because whereby should cognition be exercised,

does it not occur through objects,

which stir the senses and partly cause notions to naturally occur,

partly setting our mind in motion,

to compare and collate them,

to join them or to separate,

to process the raw material of carnal impressions into a knowledge of the objects,

is this not what experience means?

Okay, I'm sure it is clumsy. But I think I grok the author's original meaning, at least. We experience existence through our interaction with the objects around us. Classifying, smashing them together, poking and prodding. This in itself is experience.

Now the gutenberg English translation:

I. Of the difference between Pure and Empirical Knowledge

That all our knowledge begins with experience there can be no doubt. For how is it possible that the faculty of cognition should be awakened into exercise otherwise than by means of objects which affect our senses, and partly of themselves produce representations, partly rouse our powers of understanding into activity, to compare to connect, or to separate these, and so to convert the raw material of our sensuous impressions into a knowledge of objects, which is called experience?

Definitely moar wordy than mine. Pretty similar, I guess, but constructions like "faculty of cognition should be awakened into exercise otherwise than" really make me scratch my head. I think that if this was all I had, I'd have a hard time understanding wtf the original author was saying.

Or perhaps I'm just not understanding the original! And that's why ESL is bad for your mental health. What a phenomenon!

Hopper update: January 2019

January 31st, 2019

Since last updateI've been continuing to pay my technological debts, namely:

  • I managed to un-wedge my trb node1; as of today it is at block height 443238.
  • Spyked released a keccak regrind of the tmsr botworks patchset, which included a regrind of logbot_command_router_genesis. I wanted to review and sign, and so figured that this was a great opportunity to test Diana Coman's V setup. However, I had failed to understand that ave1's gnat was the standard, instead going with a heathen post-2017 gnat that ultimately failed to work with the existing implementation of V. I resigned to waiting until I had a both a saner workstation, as well as a firmer grasp on the related gnat threads in the logs.
  • With want for a saner workstation, I did some initial Cuntoo testing and ended up with two bootable Cuntoo environments. However, for whatever reason I could not log in to either of 'em, and trinque brought up the important point that I should be working to have a more substantive understanding of what the scripts are in fact doing.
  • With want for a better understanding of trinque's, I decided to step through the Gentoo handbook in order to simply install my own hand-rolled Gentoo on my x61.2 I made a point to compare what I was doing with what trinque's script was doing, and after about a week or so I managed to finally get a Gentoo installed on my lappy. The experience left me with a much deeper understanding of the installation process in general, and I actually have quite a few ideas of things to troubleshoot re: my Cuntoo attempt.

Up next:

While I could dive back into troubleshooting my login woes with Cuntoo, I look around and realize that I now have two functioning (and chroot-able) Cuntoo environments, as well as my own hand-rolled Gentoo on my x61 (complete with, at least, asciilifeform's traditional crapolade masks). I also look and see the looming pile of items I need to get back to, and I feel confident that my workstation is in better condition to start chipping away.

With that, the next item on my list is chiefly to get ave1's gnat set up, then Diana Coman's V setup set up, THEN finally read and sign Spyked's regrind. Afterwards, I'ma continue working through what's listed in

  1. with aggression patch []
  2. Non-musl. I'm just talking -A- Gentoo, of any kind; I had failed my previous "Gentoo quest" sometime in 2016 []

Initial Cuntoo Testing

January 8th, 2019

I recently grabbed an old Lenovo x611 from ebay with hopes of turning it into a proper republican workstation. As of writing this I am still working on primarily2 Debian boxen and have yet to fully complete a Gentoo install on my own iron. With my need for a sane os mounting, I figured this would be a great time to test out the latest result of Trinque's ongoing yak shaving known as Cuntoo.

The following is the results of 3 separate runs of the The target block device for each run was a SanDisk 32gb usb flash drive, and the os running the script was Debian 8. My aim was to first create a bootable Cuntoo on the usb stick, boot the Lenovo from the stick, and then obliterate its hdd with Cuntoo.

First Run - vpatch (keccak)

For my first run I used the 4.9.95-apu2 kernel config included in the cuntoo.tar.  Script ran without issue (I let it run overnight and woke up to the final prompts), however it turns out that the x61 needed another kernel. Trying to boot from the first run usb stick would result in it hanging indefinitely at the "BIOS data check successful" messaging.

cuntoo first run: loading stuck on 'BIOS data check successful'

Second Run - vpatch (sha)

After a little research I found a kernel config for the x61 (mirrored here). Script once again ran without problems, and this time it booted!

However, after multiple tries of entering what I know was the root password I set, I still was met with the "Login Incorrect" message.

cuntoo second and third runs: cannot login with either root or main user

Frustrated, I began the usual3 dance of mounting the block device, chrooting in, diddling with passwd and/or the /etc/passwd , /etc/shadow file, etc. Sadly, while educative, none of my password futzing bore any fruit so I turned my eyes to other areas.

One weird thing I noticed while poking and prodding was that some of my permissions looked a little off:

-rws--x--x 1 root root 33104 Jan  6 09:39 bin/su

At this point I was reluctant to burn too much more time identifying and enumerating screwy permissions. I decided to throw in the towel on the second run and rerun on my third usb flash drive, just for good measure.

Third Run vpatch (sha)

Third run had results identical to the second run. Meh.

So my original aims did not quite pan out, but what frustrates me more is that I'm not sure why just yet. Was it Debian strange? Perhaps just some elementary config I missed? Not sure at the moment, but on the positive side I learned a good chunk in the process4. I also have retained the Cuntoos installed on my second and third runs, so further prodding can continue down the road at least.

For now I may just try installing a Gentoo on the x61 with the hope that it teaches me a few more things I can use in later tests, as well as giving me an actual Gentoo to test from in order to rule out debianstrange. Anyways, I look forward to more Cuntoo testing in the future and perhaps a saner workstation.

  1. sadly, I couldn't find any of the 64bit x60s in working order []
  2. save for my spiffy Pizarro Rockchip []
  3. Well, usual to others versed in linux, I suppose. To me it was a very enlightening experience of just how damned easy it is to pop an os once you have physical access! []
  4. For e.g. after all of my troubleshooting I'm now quite comfortable with chroot! []

Conveyor Outlook: Now to Feb 2019

November 12th, 2018

For both my own sanity and for continued communication re: what I'm working on, I will outline what I aim to accomplish by the end of February 2019:

  1. Introduce auto-bid functionality into auctionbot. As of now, lobbesbot is the only bot with auto-bid capabilities and, imho, I did not design nor implement that functionality correctly to begin with1 and need to redo it properly.
  2. Discontinue legacy !Qauction functionality in lobbesbot.
  3. Migrate all legacy auction data2 from lobbesbot into auctionbot
  4. Implement the old-but-improved billing3

Items most-likely on conveyor for after March 2019:

  • A more automated price history for auctions and a "ticker" functionality for auctionbot
  • Redo of the remainder of lobbesbot functionality to also sit atop logbot
  • Auxiliary logotrons for #pizarro y #eulora
  1. some related mini-threads: []
  2. For the curious: 366 auctions dating back to Feb 2017 []
  3. I'ma need to retool the automated back-end bits to work with the new auctionbot database. Also need to think through how I want to report usage now that I'm only billing at a certain threshold []

Bulletin on auctionbot fees

November 4th, 2018

Some of the following may or may not be news to everyone. Nevertheless, I figure this deserves a proper post. Going forward auctionbot fees will be handled as such:

  • 20 ecu (2 satoshi) per auction hour charged to the creator of that auction1 for auctions ending with a sale
  • 100 ecu (10 satoshi) per auction hour charged to the creator of that auction for auctions ending without sale
  • Quarterly usage will still be published and deeded as before, however the creator of the auction will not receive an invoice until the amount of unpaid fees hits a threshold of 1mn ecu (0.001 BTC).2

Why have fees again?

For those that may not be aware, auctionbot fees originated as a way to discourage spam in #eulora:

mircea_popescu lobbes and by the way i'm all for your monetizing this. charge people 200 ecu / hour for successful auctions and 1k ecu/hour for auctions that end with no bids to cover for the cost of spamming the channel, and you can keep teh proceeds.

In other words, since the bot lists all active auctions in-channel every X hours, the fees exist to prevent large masses of 'junk' auctions from cluttering the logs.

Why are the fees at the rate they are today?

In late 2017 the ecu floated to 1 ecu = 0.1 satoshi3. After some discussion in the logs the auctionbot fees were lowered to the 20ecu/100ecu per hour rate stated at the top of this post.

I will continue to keep the fees relatively low.

Why is there a threshold of 0.001 BTC before collecting?

I've learned in the last year that running around each quarter and billing/collecting on what were sometimes very small sums4 was a tax on my time.

Perhaps more importantly, I do not want to discourage usage of the bot now that it has been seeing broader usage across the Republic. I believe a bill-at-threshold approach still serves the original purpose of discouraging spam, while at the same time not discouraging usage.

Of course, I will always welcome discussion on the matter.

  1. buy or sell []
  2. To put in perspective: assuming all your auctions ended in a sale, you would need to run 50,000 hours worth of auctions to see a bill. This means for users that only create, say, twelve 120-hour auctions per year, assuming they all ended in a sale it would take them ~34 years to see a bill (This, of course, assuming that fees remain unchanged.) []
  3. yes, 0.000000001 BTC, or a tenth of a satoshi []
  4. we're talking figures like 0.0000004 BTC []

auctionbot is live

October 14th, 2018

I'm pleased to report that auctionbot is now live and sitting in #trilema, #eulora, #pizarro, and #trilema-lobbes. Here's a quick run-down on usage:

Call command: !X1


!Xsell opening(ecu) duration(hours as integer) item/lot

Create an auction/order selling item/lot opening at opening(ecu), running for duration(hours as integer) hours

e.g. !Xsell 3.5mn 72 One bag of entropy

This creates a typical auction, and functions the same as the classic !Qauction from the old bot. The creator of the auction is selling some thing with potential buyers bidding the price up.

!Xbuy opening(ecu) duration(hours as integer) item/lot

Create an auction/order buying item/lot opening at opening(ecu), running for duration(hours as integer) hours

e.g. !Xbuy 3.5mn 72 One bag of entropy

This essentially creates a reverse auction. The creator of the auction is buying some thing with potential sellers bidding the price down.

!Xbid order-number amount(ecu)

Bid amount(ecu) on auction specified by order-number

e.g. !Xbid 1004 1.5bn

!Xcancel order-number

Cancel an auction that you2 created specified by order-number

e.g. !Xcancel 1003

!Xview order-number

View details on a past or current auction by order-number

e.g. !Xview 1003


List all active auctions. Note: If there are no active auctions the bot will say nothing.


List all active auctions for which you have made a bid. (Only accepted via PM)


Returns the url for this page


Ping the bot


Coming3 soon...

Assorted Likbez:

All dealings are in ecu.

Currently, 1 billion ecu = 1 btc

How to read the output of !Xlist

Take this output, for e.g.

auctionbot B#1009 O=500mn LB=499.99mn E=2018-12-07 06:34:14.465343 (16h47) >>> 2k wFF
auctionbot S#1010 O=1.08mn LB=1.13353mn E=2018-12-08 08:30:05.823023 (42h43) >>> 18096 NT q60
auctionbot S#1011 O=1.05mn LB=None E=2018-12-08 09:25:26.658053 (43h39) >>> 29873 BN q43
auctionbot --- end of auction list, 501.124mn total bids ---

'B#' or 'S#' denotes if it is a buy or sell order, followed by the order number

'O' is the opening bid, 'LB' denotes the current lead bid, and 'E' is the end date with the time remaining in hours/minutes

Everything after the ">>>" is what is being sold.

If you are unfamiliar with Euloran auctions, you may be thrown by cryptic combinations such as "BN q43" or "wFF". Note that while the bot will accept whatever strings entered for the item/lot when creating an order, nevertheless, conventions in usage emerge over time.  In the former case above, the "BN" denotes an item in the game, and the "q43" denotes the quality. In the latter case, the "wFF" stands for Wired Filthy Fiats, and has recently seen usage in Pizarro auctions.4

  1. case-sensitive []
  2. the irc nick issuing the !Xcancel []
  3. again []
  4. The ideal situation would be, of course, if I can eventually harness these conventions in order to automate price-charting. []

Seeking Forum Input: Auctionbot's Currency - btc vs ecu

September 9th, 2018

UPDATE: See thread ( Question answered. Input closed. Bot will deal 100% in ecu.


Now that I've released the command router for logbot, I've turned my attention to really trying to think through the (re)design of auctionbot. I'm currently at the point where I need to make a couple of design decisions and would like to field some input from the forum.

Question 1: Should the auctionbot deal in btc or ecu? (e.g. "!Xbid [ecu amount]" vs "!Xbid [btc amount]")

Question 2: Should the auctionbot accept bid/order amounts in either currency?1

I'm current thinking is that:

Answer to 1) I will have the thing deal in btc as opposed to ecu

Reasoning being that I need to pick one currency, and trb is the currency of the republic

Answer to 2) I will not offer any automatic btc-to-ecu conversion features.

Reasoning being I don't want to be in business of curating conversion rates for this. I'm thinking of cases like: I'm vacationing on the moon for a month. During that time ecu to btc rate changes but the bot isn't updated to reflect this change. People don't notice and chaos ensues2

Does this sound like solid reasoning? And would eulora players hate to enter their auctions in btc vs ecu?

  1. i.e. the bot converts input/output where needed to/from the currency chosen in  question 1 []
  2. e.g. someone auctions off something for their intended amount, but bot incorrectly converts it into some other amount. I'm then stuck having to unwind data after-the-fact []

logbot_command_router_python: Genesis

September 2nd, 2018

Special thanks to ben_vulpes for helping me understand the fundamental bits of the design that this specific implementation was based on.

What is this?

This is a package of .py scripts designed to 1) hook into a PostgreSQL db that is being used by a running instance of logbot or logbot-multiple-channels-corrected in order to 2) act as a configurable and extendable 'bot command router'

Where is this?

Please see spyked's Keccak regrind for the patches and this post for my signature





Install the following via your preferred method: 

logbot-genesis or logbot-multiple-channels-corrected (
psycopg2 (a PostgreSQL adapter for Python:

Press logbot_command_router_python via your preferred V:

mkdir -p ~/src/logbot_command_router_python
cd ~/src/logbot_command_router_python

mkdir .wot
cd .wot && wget && cd .. init press logbot_command_router_python logbot_command_router_python_genesis.vpatch



Bits designed to be customized to your needs:
knobs/ << Edit you postgres db connection info, bot command prefix, etc.
knobs/ << The central command router. Write or pull in your custom commands here.
commands/* << A directory to house command scripts that you can import into

To run:
Configure your bits mentioned above
Start your local postgres server and your instance of logbot or logbot-multiple-channels-corrected


Designed to communicate with a LOCAL Postgres server only, not remote. (Feel free to extend this to add that capability, however)