Doing my part for a widespread cryptocurrencies adoption, I proposed to my company to implement a system where any employee can "tip" another one using cryptocurrencies.
The idea being that if you help a coworker, deliver before it's due, impress someone with something you've done, (s)he can tip you with coins, which is less awkward than giving you $1.
When it comes to money exchanges, at least here in France, things are always complicated and there's almost no way to bring innovation in this field. For this reason I made it "fun" and chose DOGE as the tipping asset. Note that this can be changed only by modifying the configuration file.

We use https://mattermost.com as our messaging solution, and the software I wrote uses Mattermost's outgoing webhooks to summon the bot.

So here's the result of a couple of days of golang programming https://gitlab.com/iMil/derpina

Feedback very welcome, feel free to use and modify it as you wish.

I've always had this small doubt that those seed words I wrote down and encrypted might have a typo, or be wrong, and I obviously didn't want them to hang around in clear text or via the network for anything to snoop it.

So I wrote mnemocheck, basically a Dockerfile along with a small bip-utils based python script that derivates the first public address from the mnemonic, it reads them from stdin and the container should be launched with --network none.
Use it with caution, only pipe on a local, trusted machine, and using encryption tools like GPG, password-store or OpenSSL with the right algorithms.

Here it is https://gitlab.com/iMil/mnemocheck/

Version 0.8.1 has landed.

This release's main focus is HTTP mode "real life" usability.  In this mode, it is highly recommended to convert LevelDB databases (block index and chainstate) to a more concurrent-friendly database, Badger https://github.com/dgraph-io/badger. This is done in one step, using goxplorer:
It takes about 30 minutes to process all of the databases, YMMV depending on your hardware.

From there on, goxplorer will use the Badger databases instead of LevelDB. Of course, it needs to be updated regularly in order to keep in sync with the ongoing blockchain, and you have to take care not to use your node real databases as LevelDB only supports one process at a time, and this could corrupt your running database, leading to a reindexation. Here's a safe way of re-syncing Badger with LevelDB databases using an overlay filesystem https://wiki.archlinux.org/index.php/Overlay_filesystem:
leveldbctl https://github.com/yuuichi-fujioka/go-leveldbctl is a very handy tool I've contributed to in order to make it hexadecimal-friendly.

This script can be for example coupled with a filesystem event detection tool like inotify-wait in order to be launched on every blockchain change, and it can be safely called while goxporer is serving HTTP requests.

* Homepage: https://imil.net/goxplorer/
* Releases: https://gitlab.com/iMil/goxplorer/-/releases
* Source code: https://gitlab.com/iMil/goxplorer

0.6.0 is out, and with it, as promised, chainstate / UTXO support.

It is now possible to generate an address database, and use it for fast address search (UTXO only), either on the command line or via the HTTP REST/JSON server:


Note that you can search for either a full or a partial address


In the same manner, you can search for a TXID:

Homepage: https://imil.net/goxplorer/
Release: https://gitlab.com/iMil/goxplorer/-/releases
Sources: https://gitlab.com/iMil/goxplorer

Edit: release 0.6.1

Regarding the first point, you might want to have a look as goxplorer chainstate branch https://gitlab.com/iMil/goxplorer/-/tree/chainstate
I've just pushed a working version of what I hinted, you can now make a database of all addresses with a positive balance (better said, UTXOs), but it's not yet documented. The fastest way of getting this done is to 1st create the LevelDB database (can take some time depending on your hardware):

$ goxplorer -addr mkdb:anameyoulike

Then if you want to extract them to a plain text file, you can use https://github.com/yuuichi-fujioka/go-leveldbctl this way:

$ leveldbctl --dbfile=anameyoulike k > addresses.txt

The second point is on its way.

I've added a print function to ease this process in the chainstate branch. Export chainstate location and run goxplorer with the -addr print flag:

This will output every UTXO in a JSON dict to be taken individually, an array would be too big.

Example output:

The chainstate branch is actually capable of more useful actions but I'm still working on polishing and documenting them.

Release 0.5.0 is out!

Goxplorer is now able to explore blocks/index LevelDB database. This is useful when debugging and learning blockchain structure, i.e.:
More to come in this direction as mentioned in the previous post, it should open the way to faster addresses search.

I also added a toy callback, a very naive bruteforce module to test blocks against dictionary files.

Documentation/homepage: https://imil.net/goxplorer/
Release: https://gitlab.com/iMil/goxplorer/-/releases/0.5.0
Source code: https://gitlab.com/iMil/goxplorer

1. At the moment, this would take an enormous amount of time, but I am working on including chainstate support, which should help achieve something like this.
2. Same answer.

An update, only to announce release 0.3.0: Goxplorer can now be started as a REST HTTP server and thus be a backend for any type of frontend with no other dependency than the blockchain itself.

Enjoy!

Thanks a lot! And It's not its final form, I still have a couple of nice features in mind

Oh my. Why didn't I... and it actually *is* multithreaded! 

So here it is, latest version of Goxplorer has a couple of new features to help explore and discover Bitcoin's blockchain.

On the non-cosmetic side, apart from bugfixes, Goxplorer now launches block de-serialization using go routines, this simply makes a x3 performances increase.

Now on the features side:

-s permits to specify a starting block (relative, starting at 1, 0 means whole file, not block height-based)
-n can be used to only show a number of blocks
-x computes the block hash
-l uses LevelDB Block Index Record to start at a certain block hash, blkXXXXX.dat file is automatically found and loaded
-e uses LevelDB Block Index Record to start at a certain block height, blkXXXXX.dat file is automatically found and loaded
-d uses LevelDB File Information Record to load a block file from a certain date, blkXXXXX.dat file is automatically found and loaded
-tx loads and de-serialize a single transaction

"Real-life" examples are available on the project's GitLab https://gitlab.com/iMil/goxplorer

Bonus track, I couldn't find a working example of Bitcoin's LevelDB usage in golang, so I wrote blockchain/leveldb.go from scratch, it might help some Go developers.

Comments and ideas are very welcome.

Edit: added -e
Edit2: added -d

Not sure if sarcastic 

Thanks anyway, and I have many things cooking as for goxplorer future, notably a huge speed boost using both goroutines and block index. Latest commits fixed various bugs and adds customizable helper functions.

FWIW I sent him an email on November 3 to let him know about the Dockerfile and thank him for his work and he never replied... I just assumed he was busy.

Hi,

A couple of weeks ago I started a toy project in order to dig into blocks structure, and one thing leading to another, it evolved into a pretty usable block file parser Go package.
I am aware of btcsuite, but TBH I found its documentation really hard to read and the project way too large for the simple task I wanted to achieve, so I took the opportunity.

So here it is, I present you Goxplorer (pun intended) https://gitlab.com/iMil/goxplorer, it supports pretty much all locking mechanisms including natives and P2SH embedded SegWit ones. It has the ability to add callbacks for every parsed transaction and/or block, which makes it fun to play with.

It still needs more documentation and testing, but I thought you might find it useful.

Hope you like it,

Cheers,

iMil

Thanks a lot for this Jean-Luc, great software. And FWIW, I wrote a Dockerfile so anyone can easily and securely run it. It can be found here https://gitlab.com/iMil/vanitysearch-docker

/r/eBTC/ banner, top right, pepe.

Guys, I hate to break it but... look at the picture upper right of their Reddit page. Think.

Are they? because if they are it doesn't show up much on their GitHub repository: https://github.com/signatumd

Well I already can tel you how to build it, tell me if you also have poor performances:

This is for Debian, which I use. I will assume you already have the AMD SDK installed in /opt


At this point you'll have sgminer installed in /usr/local/bin and you can start it with:


Of course you'll have to modify the values to match your worker and pool.

Please tell me what hashrate you get!

No Linux version yet