dewyatt / bitsee Goto Github PK

The href is currently a placeholder.

Currently we look at outputs by type (multisig, pubkeyhash, nulldata, ...) which does generally make sense.
However, it also makes sense to view them by value since it's common to use the same small amount for embedding data in a transaction.

Messages can be sent via vanity addresses and it should be possible to pick up on these using a dictionary.

I have been facing an issue for the past two days, trying to actually use the tool. I did follow the instructions exactly as stated in the readme.
Several issues:
The backend loads fine on port 3000 of localhost but it is empty. If I try to:

• bundle exec rails utils:load_test_data
  I get as a response: rails aborted! Missing environment variables
  

• If I do try the single transaction or a selection of blocks commands i.e: bundle exec rails utils:scan_blocks BTC_USERNAME=user BTC_PASSWORD=password FILES_PATH=~/bitsee/public/files/ FILES_URL=/files BLOCK_BEGIN=230037 BLOCK_END=230100,
  I do get a different response: rails aborted! Errors in response
  

• And to actually confirm that I do have some sort of connection, if I do supply wrong credentials in the BTC_USERNAME and BTC_PASSWORD fields, I do get a response from the RPC client of Bitcoin: ThreadRPCServer incorrect password attempt from 127.0.0.1:33154

So what might be the issue that I am facing here? Is this something with the working environment and incompatibility with updated gems or something I am missing out?

This requires better multi-tx file support because we will need to mark transactions as already consumed as part of a multi-tx embed.

This would eliminate an external gem so should be considered.

These all need to consider that io.read may return nil.

Generally a spent output is not going to be embedded data. This could cut down on false positives.