26

The first question one needs to ask before even considering adaptive blocksize limits is: Can a fee market actually work in the absence of a base emission? We first consider a blocksize large enough (or effectively infinite). In this scenario competition among miners will drive fees towards zero since there is no scarcity. This will in turn ...


21

Starting with v0.10.1, there is now a command print_coinbase_tx_sum that give you this information.


13

There is no such command. However, it'd be easy to add. Feel free to add a request for this on https://github.com/monero-project/bitmonero/issues


7

While running monerod, type in the following command: print_coinbase_tx_sum <start height> <block count> This will sum all the coinbase transaction outputs for the blocks defined by the arguments, while also showing how much is from emission and how much from fees. Example output of the command print_coinbase_tx_sum 0 1000: Sum of coinbase ...


6

What if there was no gold to mine? The fact that it might be more efficient or beneficial to mine rather than buy from a collector adds needed complexity to market decisions. Beanie Babies were limited, and nobody gives a shit about them and I doubt even if they were infinitely divisible it would make a difference. Why not limit bitcoin to 10? why not 10 ...


6

the miner, who found the block, will be rewarded with some Moneros, in the expenses of the sender. That also happens, and it is called a transaction fee. Transaction fees are small: 0.002 XMR (per output, or Kb, I am not sure). On the other hand, what you are observing is the block reward of about 10 XMR per block found which seems wasteful at first glance,...


5

As far as I understand, this is to make sure that the coins were mined on the longest blockchain, and thus the longer "delay" of 60 blocks is meant as a safeguard against transactions becoming invalid because of blockchain reorganizations. These might change several dozens of blocks sometimes. While 60 blocks should typically be enough, I have seen some ...


5

It must be impossible. The underlying math is such that it is provably impossible. So no, it's not theoretically possible. Theoretical possibility would mean a broken coin. I could imagine 2 ways to create coins in a TX: Successfully double-spend the same output. However, this is not possible because of the key images mechanism. Cheat the sum(in) == sum(...


5

The person(s) mining would need to provide these fields. They are normally created by the sender of a normal transaction whereby a new private / public key pair and corresponding shared ECDH secret is created. In this case the person(s) who successfully mined a block gets to "send" themselves the block reward. But instead of sending it as RingCT type 0 (more ...


5

Question: is the unlock block height the first block that an output is spendable, or the last block it is unspendable? ... can the coinbase be spent in block 61 or must it be at least block 62? 61.


3

You are correct to point out that if you send exactly 3.5999749793 XMR (3.6 XMR - e.g. 0.000025020730 XMR tx fee) to your recipient, by referencing 11 outputs in your ring signature, one of which is exactly 3.6 XMR, they will have a high chance of guessing that you are spending the mined output. This, however, is a somewhat contrived example. Most of the ...


3

Why does Monero split up the rewards in this instance? This answer requires a bit of history first to be sufficiently explanatory. In the first years of Monero's existence amounts were not encrypted yet. In addition, output amounts were "split" into denominations to the power of 10 to ensure they could be used as decoy outputs (i.e. ring partners). Thus, ...


3

The Coinbase can be spent after 60 blocks. See CRYPTONOTE_MINED_MONEY_UNLOCK_WINDOW


3

I exported the blockchain from another node I have and imported to the failing node. Seems to have fixed the issue and it is now syncing and up to date.


3

Transaction fees does not disappear. They are earned by the miners as part of the block reward, so they stay in the available money supply.


2

You can print the total coin supply with the command print_coinbase_tx_sum However, this assumes that there were no issues with transaction construction. In this case, the supply can be audited afterwards to see if there were any errors. Here is the information for a vulnerability that was found with Monero and patched before exploitation: In Monero we've ...


2

This question has a fundamental misunderstanding of money supply and the link with coinbase transactions. You would be right in a perfectly secure system, the coinbase transactions are the only way to add coins to the money supply. The reality however is different. Bugs in the protocol (like the infamous keyimage bug that allowed the creation of infinite ...


2

Cant add to the comment, but like he was saying, the transaction fee does not disappear. Sure it's not awarded right away by your pool, but it's awarded to someone. If its 1000 block reward, then the total supply would go up by 1000, regardless of the fee.


2

moneropedia Stealth addresses are an important part of Monero's inherent privacy. They allow and require the sender to create random one-time addresses for every transaction on behalf of the recipient.


2

Because miners are free to put whatever they want in there. For example, if you parse the 2nd as ASCII codes, it can be decoded to: 4,QAy^0P<ºÈ±ùGÛg¥g=ÆúòVø9QÇ?MinerGate001!>պ⨪Ëq©ä9{ê¤^KPÀÙ^ñÈýdÇG)ù


2

This option is available for the in-built miner. Reviewing how it's used: Its expected format is one base64 string per line. When the miner requests a block template to mine, it adds the current index line from the file as the extra_nonce field in the block template - this gets placed in the tx extra field. When the miner finds a block, it increments the ...


1

Why would you remove extra ? It's in there. See cn_deserialize.cpp, to which you can give the hex dump of that tx: cn_deserialize --input aaaaaaaaaaaaaaaaaaaa This will show you the tx key.


1

In the miner code, there is a request_block_template function, which requests a new block template to the daemon using the miner's address. If and when the miner finds a block, she will create it from the block template that contains her address. If the block is accepted by the network, her address will be credited with the block reward.


1

The ecdhInfo fields are encrypted from the sender to the receiver using the shared secret derived from the ECDH exchange. They contain the mask that "hides" the amount being transferred in the public commitment, and the amount that the mask is hiding. The receiver verifies that the public commitment = mask + amount (hand-waving away the EC arithmetic ...


Only top voted, non community-wiki answers of a minimum length are eligible