12

You can put potentially any data into tx_extra and it will be stored on the blockchain with your transaction, only accessible with your keys. This however, will bloat your transaction size and your transaction will be more expensive as you have to pay per kb. For now, beside the elastic blocksize limit (median of last 100 blocks * 2) there is no maximum how ...


5

The basics are already here: encrypted payment IDs are private information encrypted by the sender, which only the recipient can decrypt. If the sender and the recipient are the same party, you can store data that only yourself is able to recover. A similar system could be used to enable "chat like" behavior. Transactions would have to be marked as non-...


5

The use case I had in mind when I wrote this code is to run daemons on different network interfaces, or on different network protocols, using the same database. E.g., if you want to use different bandwidth limits on one interface vs another, or if you want to run a daemon on TOR simultaneously with a daemon on clearnet. Or, you want to run a public node (...


5

On Windows, this can actually be done fairly simply. These options are slightly technical, but not terribly difficult, and only have to be done once. There are a couple quick ways. Option 1 - Make a copy of the shortcut link used for launching the GUI (or monerod). Then right-click the copied shortcut to edit the shortcut's properties; and then add at ...


4

Blocks, txs, outputs, and spent keys are already indexed. What else is there? The complete DB schema is here https://github.com/monero-project/monero/blob/master/src/blockchain_db/lmdb/db_lmdb.cpp#L148


4

You'll have to write some code for this. There is a BlockchainDB::for_all_transactions function which can run a callback through all the transactions in the db. See the blockchain_dump.cpp file for an example. The callback can simply output the hash for all the transactions with a mixin of 10 (mixin being one less than the number of inputs in each vin array ...


4

This question basically pertains to where monero-blockchain-import stores the imported blockchain by default. monero-blockchain-import uses the following default directories to store the imported blockchain: Windows: C:\ProgramData\bitmonero\lmdb Linux and Mac OS X: ~/.bitmonero/lmdb Note that, by default, both C:\ProgramData\bitmonero\lmdb and ~/....


4

Unplug/disconnect internet, monerod --allow-local-ip --add-exclusive-node XXX.XXX.XXX.XXX With the exclusive argument you may not even need to uplug or disconnect from the internet.


3

When a block is received while the node is not syncing through backlog, it is validated on the spot. If the node is doing backlog syncing, the block is placed in a queue, and blocks in the queue will be validated in height order. Since miners are typically always up to date, the former will apply, and blocks will be verified as soon as they are received. "...


3

Understanding the structure of Monero's LMDB and how explore its contents using mdb_stat Firstly, mdb_stat is a tool to get status information about the database environment, not to explore its contents. Quoting the description directly from the mdb_stat manual: The mdb_stat utility displays the status of an LMDB environment. I am assuming querying it ...


3

Monero targets a new block every 2 minutes, so if we set H as the current block height, N as the current timestamp, T as the past timestamp of the datetime you want to know the block height of, then: H - (N - T) / 120 Gets you very near. Blocks aren't mined exactly every 2 minutes, so there will be fluctuation. To narrow down further, you can then use a ...


3

Both cases are possible. Filler.


2

With 0.11 (and possibly 0.10.3.1, though I'm not 100% certain this was ready then), there is no particular precautions to take in order to share a database between two daemons. Pointing the daemons to the same directory using --data-dir should be safe. I'm not sure this has been tested a lot, however, so if anything like corruption should happen, please ...


2

Firstly, blocks don't get "added to the pool". A wallet instructs a daemon to broadcast a transaction which gets added to the transaction pool. A miner constructs a block template by bunching transactions that are in the transaction pool, then mining that block template. When a miner successfully mines a block, it is broadcast to the network, and if valid, ...


1

No, deleting data.mdb will not delete your wallet. The data.mdb file is the blockchain. Deleting it does not affect your wallet. Your wallet has a name of its own. You'll know what it is because it has at least one sister file that holds its keys. In other words, you'll know what "your_wallet" is because you'll see your_wallet and your_wallet.keys (...


1

One simple way is to call the daemon RPC's method getblock. From this you can get the result.blob (the data to be hashed) and from the result.block_header.hash, the expected hash result.


1

The simplest and most portable approach is provided by dEBYUNE above. The --data-dir can also be defined in the monero node's configuration file so it does not have to be passed as an argument of the monerod CLI. Otherwise, a UNIX only approach is provided below. Step 0 - make sure monerod is not running Step 1 - make sure the owners, groups and ...


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