< bitcoin-git> [bitcoin] csdnnet opened pull request #11572: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/11572
< bitcoin-git> [bitcoin] fanquake closed pull request #11572: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/11572
< meshcollider> fanquake is so quick
< * LumberCartel> agrees
< fanquake> achow101 Looks like the fall through warnings have been silenced upstream, so we can probably pull though changes down, and then figure out why our silencing isn't working.
< bitcoin-git> [bitcoin] fanquake opened pull request #11573: [Util] Update tinyformat.h (master...pull-upstream-tinyformat) https://github.com/bitcoin/bitcoin/pull/11573
< fanquake> achow101 thanks for verifying so quick
< sugarcoin> Hi! I have a quick question that I have not been able to answer by browsing through the documentation or online... Is there a way to sync the core up to a particular transaction height? I'm looking to get a list of UTxO as of a particular height. Thanks!
< sugarcoin> block* height
< sipa> i believe there is a -stopatheight option
< sugarcoin> Thanks, Sipa!
< wumpus> new in 0.15
< sugarcoin> Yup. That's probably why there's not much about it online.
< sugarcoin> Thanks both.
< bitcoin-git> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/ba216b5fa63e...bb9ab0fccfba
< bitcoin-git> bitcoin/master f8c6697 Evan Klitzke: Fix automake warnings when running autogen.sh
< bitcoin-git> bitcoin/master cc5c39d fanquake: [Build] Add AM_OBJCXXFLAGS and QT_PIE_FLAGS to OBJCXXFLAGS to future-proof darwin targets
< bitcoin-git> bitcoin/master bb9ab0f Wladimir J. van der Laan: Merge #11541: Build: Fix Automake warnings when running autogen.sh...
< bitcoin-git> [bitcoin] laanwj closed pull request #11541: Build: Fix Automake warnings when running autogen.sh (master...fix-automake-warnings) https://github.com/bitcoin/bitcoin/pull/11541
< Alkhara> with the current master release of Bitcoin, is the 80 extra bytes OP_Return still available to embed data? or was that removed?
< wumpus> why do you think that was removed?
< Alkhara> Wasn't the method changed? Looking at Blockchain.info instead of it saying OP_Return now it's PUSHDATA
< wumpus> as far as I know nothing about that changed
< wumpus> blockchain.info might have changed their site but that's nothing to do with bitcoin core
< arubi> there was always a pushdata after the op_return if there was any data to be pushed. op_return isn't op_graffiti . it just means that the script is halted when it's executed
< wumpus> yes
< Alkhara> Ahh I see, alright thanks
< Alkhara> This may not be the right place for this and feel free to tell me if it's not, but is there a reference sheet anywhere that points to the current value locations of Bitcoin's main variables? For example, max_coin_count is located in xxx.cpp. I am looking to fork for a project of mine but C++ skills are slowly coming up from nothing.
< wumpus> no, not really, there is general software to cross-reference C++ projects though
< wumpus> grep is also your friend
< Alkhara> Yeah, that's what I was about to try using, just clone it and search for the terms I know of anyway
< Alkhara> So in amount.h is this the actual token cap? static const CAmount MAX_MONEY = 21000000 * COIN; the comment above it makes it sound like it's just a logic check to prevent someone who finds a bug to create coins outside of new blocks?
< wumpus> indeed, it's just a logic check, the miner reward determines how much coins actually enter the system
< Alkhara> Oh I see, so it just follows the miner reward path down to zero and that just ensures that the math checks out in the end.
< wumpus> it's basically just to avoid integer overflow
< Alkhara> ahh gotcha
< wumpus> there is no check that there are not more than MAX_MONEY in utxos, a single output cannot be larger than that, and the total output of a transaction cannot be larger than that
< Alkhara> ok yeah makes sense
< Alkhara> What was GetBlockValue replaced with when main.cpp went away?
< Alkhara> ahhhh sneaky sneaky, changed it to GetBlockSubsidy in validation.cpp
< Alkhara> Anyone know where to make the change to set the address prefix by default of of 1 ?
< Alkhara> off of*
< sipa> Alkhara: src/chainparams.cpp, base58Prefixes
< Alkhara> tyty Sipa
< Alkhara> When creating a new Genesis block, you are supposed to initialize with a new pszTimestamp, nTime, and nNonce right? I see where I can change the pszTimestamp, but would you declare a new nTime and nNonce value by adding line to this? or would they get passed as args?
< Alkhara> static CBlock CreateGenesisBlock(uint32_t nTime, uint32_t nNonce, uint32_t nBits, int32_t nVersion, const CAmount& genesisReward)
< Alkhara> {
< Alkhara> const char* pszTimestamp = "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks";
< Alkhara> const CScript genesisOutputScript = CScript() << ParseHex("04678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef38c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f") << OP_CHECKSIG;
< Alkhara> return CreateGenesisBlock(pszTimestamp, genesisOutputScript, nTime, nNonce, nBits, nVersion, genesisReward);
< Alkhara> }
< Alkhara> like just add 2 new lines below const char* pszTimestamp?
< BlueMatt> Alkhara: please take this to #bitcoin
< sipa> i'm happy to answer questions about the codebase here
< sipa> but it's not the place to ask for a tutorial to create your own currency
< Alkhara> I mean my project isn't even going to be a competing currency, more of a service, and for some reason I am banned from #bitcoin even though I don't think I have ever been there.
< sipa> well, regardless this is not a place to ask for a tutorial
< sipa> perhaps you can try bitcoin.stackexchange.com
< Alkhara> k thanks