The British courts will fuck him up . I certainly hope so. |
|
|
|
Wow, that's a nice dip. How could you not stack some sats?
Oprah said double-dipping is bad. |
|
|
|
Haven't sold anything yet. Looks like a perfect bulltrap. Stop whining and get back to hodling/buying!  Bulltrap or Beartrap? In which Phase are we yet?  We're in the maths & science phase. |
|
|
|
How long does a transaction stay in the mempool?
I payed way to little and now I'm not getting any confirmations.
RBF. Pamp it. |
|
|
|
Finished most of the code now, and almost all is covered by test units  Great. I'm still syncing libbitcoin-server testnet after modifying bs.cfg few times (had to change many checkpoint, BIP checkpoint and other variable specific for testnet). Edit: i didn't know libbitcoin-server is fragile. Power outage and stop the application using SIGTERM (because it didn't respond to Ctrl-C and SIGINT) causes the database to corrupt and the only way i know to solve the problem is by sync from 0 again. Edit 2: Since i use regular computer which isn't turned on 24/7, i decide to turn off the computer. However libbitcoin-server doesn't respond to Ctrl-C and SIGINT again. I waited about half an hour where there's no progress mentioned on console and log file. I'll just wait until libbitcoin v4 is stable. If you have an unstable power source or something, you can enable the "flush_writes" option in the config file. This will slow down the sync a bit, but it should avoid corrupting the databases. By default libbitcoin decides to keep most of the stuff in memory and just do periodic writes to disk. But yeah, v4 is still in development so there are bugs for sure. However, Eric tells me that he's back on working on libbitcoin full time again so I expect it to be more stable sooner than later. On my local testnet libbitcoin-server, I modified the configuration to the testnet values and didn't change anything else except "use_libconsensus=true" from the defaults. The comments in the config file tell you what needs to be changed to work on mainnet/testnet. |
|
|
|
It's going to get much, much worse. Easy to see when you do the math.
Teach me. |
|
|
|
@LinaSeiche
They say he has a whole BTC
Long gone times  |
|
|
|
Good morning Bitcoinland. I see we're about halfway back up after a little $3k dip... currently $61345USD/$76785CAD (Bitcoinaverage). Still in the $6xxxx range. Go Bitcoin go. Bought a physical painting today. Feels much better than the NFT hype.
No freaking kidding. An actual painting beats a virtual painting just like driving an actual car beats looking at a car ownership document, swimming in a private lake beats looking at a picture of a lake, or sex with a real women beats an inflatable plastic doll. You can tell a lot by the smell. Can you still smell the aroma of the paint? Is it as nice as the smell of a new car, a lakeside breeze, or a horny woman? Smells like oil paint. It's good |
|
|
|
|
Bought a physical painting today. Feels much better than the NFT hype.
|
|
|
|
Finished most of the code now, and almost all is covered by test units libbitcoin-server v4 still needs some code written, regarding tx broadcasting, but hopefully this will be finished soon. |
|
|
|
Good morning WO! Movement is positive, times are happy |
|
|
|
Good afternoon WO!
Observing @ $63,090
It's time for $100k!!!
 |
|
|
|
Strange. if this prefix is correct, then the binary should be in $HOME/.local/bin/bs, and the config file should be in $HOME/.local/etc/libbitcoin/bs.cfg
You can run it with the full path, after you configure bs.cfg. If they're not there, then something did error (or you perhaps ran install.sh with another user's privileges so it ended up in a different $HOME, like /root/.local).
I'm sure i didn't use different user or sudo to run the script. However, i solved the problem simply by replacing $HOME/.local with absolute path (on new directory solely for libbitcoin). I can run ./bs -v without any problem. Version Information:
libbitcoin-server: 4.0.0
libbitcoin-protocol: 4.0.0
libbitcoin-node: 4.0.0
libbitcoin-blockchain: 4.0.0
libbitcoin: 4.0.0
Now i just need to configure libbitcoin-server and perform initial sync. However, i just notice i'll have 2 copy of Bitcoin blockchain with different format (owned by Bitcoin Core and libbitcoin), so i'll free my HDD for libbitcoin's blockchain. There shouldn't be any more problem and i assume libbitcoin will take few days to sync since i use HDD before i can test Obelisk. For what it's worth, the autotools is generally the tool that is ran in a standalone context. The install.sh script also downloads all other necessary dependencies, like libbitcoin-system, and libbitcoin-node and does all that for you transparently.
Yeah, i noticed that. Ok, glad you got it set up. One thing I recommend is to first sync testnet, it's about 30 gigabytes only and play with that before going mainnet. |
|
|
|
|
Another day another nice 64k surprise!
Good morning WO!
|
|
|
|
|
Show Posts
