< achow101>
Is there any way in Bitcoin Core to mine to a specific address when in regtest mode?
< warren>
achow101: you can construct a valid block outside of core and submit it
< achow101>
warren: I suppose I could do that, but that just make things annoying since this is just for rpc tests for Armory. Do you know if the Bitcoin Core rpc tests have mining implmented in them? If so I can just borrow that
< gmaxwell>
achow101: import the key it choses into armory? hm. we could make the generate take an option for the output, I guess. it seems like a reasonable request.
< achow101>
warren: can't import the key since armory doesn't accept compressed keys yet.
< achow101>
well it looks like the rpc tests do have regtest mining stuff there, but I'm not sure that it will work well with not being in the Bitcoin Core project.
< GitHub32>
bitcoin/master 110b62f Patrick Strateman: Remove vfReachable and modify IsReachable to only use vfLimited....
< GitHub32>
bitcoin/master 9f14e5a Wladimir J. van der Laan: Merge #7553: Remove vfReachable and modify IsReachable to only use vfLimited....
< GitHub55>
[bitcoin] laanwj closed pull request #7553: Remove vfReachable and modify IsReachable to only use vfLimited. (master...2016-02-17-reachable) https://github.com/bitcoin/bitcoin/pull/7553
< GitHub23>
[bitcoin] laanwj closed pull request #7640: Removes forward slash (/) from user agent in peers tab UI. (master...master) https://github.com/bitcoin/bitcoin/pull/7640
< jonasschnelli>
wumpus: I tried to change the wallet init (instantiation) with a scoped pointer. But IMO the idea of scoped pointers is that you can really leak them and therefore you can release them and return them to somewhere outside of the scope (http://www.boost.org/doc/libs/1_59_0/libs/smart_ptr/scoped_ptr.htm).
< jonasschnelli>
*you can't release them*
< sipa>
use a const scoped pointer :)
< sipa>
those can't be released
< jonasschnelli>
sipa: IIRC, you can't release a non-scoped pointer. Isn't that the idea of the scoped pointer? Avoid leaks?
< jonasschnelli>
*a non-const scoped pointer*
< * jonasschnelli>
wishes a slack like re-edit function in IRC with history
< sipa>
what is a non-scoped pointer?
< sipa>
ah
< sipa>
oh, i'm confusing with unique_ptr
< morcos>
hmm... so i was hoping to write the BIP112 rpc tests with the {locktime OP_CSV OP_DROP} in the scriptPubKey to keep things as close to actual usage as possible
< morcos>
however it seems like it'll be quite difficult to figure out how to sign anything like that.. none of the existing tools will do it right?
< GitHub16>
[bitcoin] achow101 opened pull request #7668: Fix history deletion bug after font size change (master...rpcconsole-hist-fix) https://github.com/bitcoin/bitcoin/pull/7668
< sipa>
morcos: see #7601 :)
< sipa>
(cltv, not csv, though)
< morcos>
yeah... might be nice to have some kind of more generic signing functionality for manual tx creation.. or including the python code for that or something.. anyway, i'm going to cheat and put it in scriptSig..
< wumpus>
jonasschnelli: depends on the kind of scoped point, a auto_ptr (and its c++11 replacement, unique_ptr) can defnitely be released
< wumpus>
this is used in CreateNewBlock for example
< jonasschnelli>
wumpus: thanks. Will have a look there.
< cfields_>
jonasschnelli: what are you trying to accomplish?