That faucet I linked you to provides 0.089 per request (and currently has 8.something).  I'm sure you can turn up another one or two of these testnet faucets pretty easily.  If you have 0.2-0.3 testnet coins, surely that's enough to test a large number of transactions.  For one thing, is there some reason why you don't control the receiving addresses?  If not, you just send coins back and forth as you're testing whatever you're testing.  Even if you can't recover them, at 0.3 testnet BTC you'll have 30000000 satoshis to play with.

Surely this is enough.  Anyway, I don't resent you posting here to look for testnet coins, I'm just saying how I got them when I needed them and what I did with them when I was done.

Having coins spread out over the most addresses is (apart from the CLAM distribution) finanically de-incentivized since you pay for each of those inputs when you try to spend something in the way of more-inputs->larger-transaction->larger-fees.  I also realize that you could have lots of inputs at the same "address" but having a value spread across many addresses means you're definitely going to have separate inputs for each when/if you try to spend them.

Thanks!  I also rhappened to re-look over the original whitepaper and I noticed (for the first time) the section on "reclaiming disk space".  I guess I'm trying to figure out what the disadvantages are (if any) over running a pruned node vs non-pruned.

EDIT: I found some further notes about pruning in the release notes for 0.11: https://github.com/bitcoin/bitcoin/blob/v0.11.0/doc/release-notes.md#block-file-pruning

Have  you tried DannyHamilton's ignore list?  It probably needs an update (last jan 2016) but it's a good start: https://bitcointalk.org/index.php?topic=973843.0

I was away from following development on core for some time.  Last time I was up-to-speed pruning was just starting to be implemented.  @achow101: where I can read about the pruning implementation (obviously I can study the source, but I suppose there's a writeup somewhere)?

When I was in need of testnet coins I got them from a faucet service.  Here's the first one a search turned up:

https://tpfaucet.appspot.com/

It's been picked up by the network.  I see it in the pool on blockchain.info (for example).

https://blockchain.info/tx/4a6f6b89eab7420ef54ae3d7725bf524eb14c6f797cf96fd2afdf669254b9965

Maybe you're wanting to add more fee?

So, in your firewall, are you doing nat to map 18333 to 8332?  If one program is listening on a different port than the other is sending on then that seems like the place to look.

Again, sorry this is so general, I don't know your script.  On GNU/Linux, you generally find logs for system programs in /var/log/.  I've used apache more than nginx, so /var/log/apache2/ for those logs.  nginx may be in /var/log/nginx (that's where I'd look).  I suppose I was thinking more about just debugging using echo >> somelogfile in your php program.  And, since it's been a while since I messed with bitcoin rpc, I can't remember if/where rpc logs are but maybe in ~/.bitcoin/debug.log

The latter is trivially easy, right?

No reason to think he isn't still sig spamming and account farming.  He's definitely still doing all the other stuff he used to do.

I'm not familiar with this market script.  But did you check the port your bitcoind is listening on is the same one that your market script is sending on?  (I guess I'm assuming a tcp/ip communication channel)

In general, can you create (or read from) logs on both ends to see what's going on?  If your bitcoind isn't responding at all to the market script, can you log whether you got any reply at all?

Just some ideas.

You say you can issue bitcoin-cli commands all day, so double check the port password, rpcuser, etc from your bitcoin.conf are the same values your market script is using.

Love how every single QS "rebuttal" in this thread ends with "are you Lauda?".  It's just that our own favorite sockpuppeteer can't help but thinking that everyone else works the way he does: an army of sockpuppets to try to keep bumping and echoing.  QS: you've been caught at it again and again, do you remember when you said you were going to leave the forum?

Okay, I'll bite, I'm curious.

I see this in OP RETURN:

 "jLN Augustana College Old-Main.jpg Reconstruct with data preceding redeemscripts"

So I guess you've got the jpeg file in there somewhere (I didn't look at the whole raw transaction or try finding it).

What was the point here?  What am I missing?

Can you download them and then do sha256sum on them?  That will answer your question definitively (at the level of bitwise difference between your downloaded binaries).

I thought OP was talking about the time to break symmetric encryption on a file containing the mnemonic.   I just learned something.

I can't answer all of this question, I don't know what kind of symmetric encryption algorithms trezor is providing.  I can tell you that the number of guesses per second depends on the implementation of the cracking script and the hardware it's running on.

Now, assuming your additional passphrase is sufficiently random (not something that could be found in a rainbow table), and assuming some modern encryption procedure, like, say AES 256 (https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) then unless these hypothetical ppl are throwing tons of resources at cracking your wallet, it should be pretty difficult.  On the other hand, if they have huge, dedicated compute clusters then maybe they'll find your password really soon.  It's all about resources.

And when each response to "show us something you've worked on" or "why don't you take this on and join the project" is replied to with "You fools!  MWA HAHA", then that self-proclamation starts to look incredibly weak, imo.

My reading was that Troll Buster's points were all replied to by gmaxwell.  Once you cut away all of the "stupid", "worthless", etc, invective there were a few criticisms in there and I'm pretty sure they were addressed.  Then, when Mr. Buster continued with the "you're all so stupid" style posts, I think people naturally respond with "ok, can you, like, show us why you're so smart", to which Mr. Buster sorta ran away screaming:




Hardly seems unreasonable to reply with technical answer to the few bits of detail in Troll Buster's post (which gmaxwell did) and then to address his invective and screaming by asking him to show something more productive than insults.

This should be an easy one for someone here.

I was thinking about turning on pruning to save some disk space.  Do I need to recompile?  I don't recall seeing any options for pruning when I ran


last time I built bitcoind.  Alternatively, is this something I stick in my .conf file?

CLAMs were also distributed to Litecoin and Doge wallets, just for the record.  You guys remember Doge?