| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
It causes link errors at least on mac
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Daemons intended for public use can be set up to require payment
in the form of hashes in exchange for RPC service. This enables
public daemons to receive payment for their work over a large
number of calls. This system behaves similarly to a pool, so
payment takes the form of valid blocks every so often, yielding
a large one off payment, rather than constant micropayments.
This system can also be used by third parties as a "paywall"
layer, where users of a service can pay for use by mining Monero
to the service provider's address. An example of this for web
site access is Primo, a Monero mining based website "paywall":
https://github.com/selene-kovri/primo
This has some advantages:
- incentive to run a node providing RPC services, thereby promoting the availability of third party nodes for those who can't run their own
- incentive to run your own node instead of using a third party's, thereby promoting decentralization
- decentralized: payment is done between a client and server, with no third party needed
- private: since the system is "pay as you go", you don't need to identify yourself to claim a long lived balance
- no payment occurs on the blockchain, so there is no extra transactional load
- one may mine with a beefy server, and use those credits from a phone, by reusing the client ID (at the cost of some privacy)
- no barrier to entry: anyone may run a RPC node, and your expected revenue depends on how much work you do
- Sybil resistant: if you run 1000 idle RPC nodes, you don't magically get more revenue
- no large credit balance maintained on servers, so they have no incentive to exit scam
- you can use any/many node(s), since there's little cost in switching servers
- market based prices: competition between servers to lower costs
- incentive for a distributed third party node system: if some public nodes are overused/slow, traffic can move to others
- increases network security
- helps counteract mining pools' share of the network hash rate
- zero incentive for a payer to "double spend" since a reorg does not give any money back to the miner
And some disadvantages:
- low power clients will have difficulty mining (but one can optionally mine in advance and/or with a faster machine)
- payment is "random", so a server might go a long time without a block before getting one
- a public node's overall expected payment may be small
Public nodes are expected to compete to find a suitable level for
cost of service.
The daemon can be set up this way to require payment for RPC services:
monerod --rpc-payment-address 4xxxxxx \
--rpc-payment-credits 250 --rpc-payment-difficulty 1000
These values are an example only.
The --rpc-payment-difficulty switch selects how hard each "share" should
be, similar to a mining pool. The higher the difficulty, the fewer
shares a client will find.
The --rpc-payment-credits switch selects how many credits are awarded
for each share a client finds.
Considering both options, clients will be awarded credits/difficulty
credits for every hash they calculate. For example, in the command line
above, 0.25 credits per hash. A client mining at 100 H/s will therefore
get an average of 25 credits per second.
For reference, in the current implementation, a credit is enough to
sync 20 blocks, so a 100 H/s client that's just starting to use Monero
and uses this daemon will be able to sync 500 blocks per second.
The wallet can be set to automatically mine if connected to a daemon
which requires payment for RPC usage. It will try to keep a balance
of 50000 credits, stopping mining when it's at this level, and starting
again as credits are spent. With the example above, a new client will
mine this much credits in about half an hour, and this target is enough
to sync 500000 blocks (currently about a third of the monero blockchain).
There are three new settings in the wallet:
- credits-target: this is the amount of credits a wallet will try to
reach before stopping mining. The default of 0 means 50000 credits.
- auto-mine-for-rpc-payment-threshold: this controls the minimum
credit rate which the wallet considers worth mining for. If the
daemon credits less than this ratio, the wallet will consider mining
to be not worth it. In the example above, the rate is 0.25
- persistent-rpc-client-id: if set, this allows the wallet to reuse
a client id across runs. This means a public node can tell a wallet
that's connecting is the same as one that connected previously, but
allows a wallet to keep their credit balance from one run to the
other. Since the wallet only mines to keep a small credit balance,
this is not normally worth doing. However, someone may want to mine
on a fast server, and use that credit balance on a low power device
such as a phone. If left unset, a new client ID is generated at
each wallet start, for privacy reasons.
To mine and use a credit balance on two different devices, you can
use the --rpc-client-secret-key switch. A wallet's client secret key
can be found using the new rpc_payments command in the wallet.
Note: anyone knowing your RPC client secret key is able to use your
credit balance.
The wallet has a few new commands too:
- start_mining_for_rpc: start mining to acquire more credits,
regardless of the auto mining settings
- stop_mining_for_rpc: stop mining to acquire more credits
- rpc_payments: display information about current credits with
the currently selected daemon
The node has an extra command:
- rpc_payments: display information about clients and their
balances
The node will forget about any balance for clients which have
been inactive for 6 months. Balances carry over on node restart.
|
| |\
| |
| |
| | |
9447e72 cryptonote: add function to get weight from a pruned tx (moneromooo-monero)
|
| | |
| |
| |
| |
| | |
The weight of the prunable data is deterministic from the
unpruned data, so it can be determined from a pruned tx
|
| |\ \
| | |
| | |
| | | |
be82c40 Support median block size > 4 GB (moneromooo-monero)
|
| | | |
| | |
| | |
| | |
| | | |
add a 128/64 division routine so we can use a > 32 bit median block
size in calculations
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
7fdaa82 Fix build on FreeBSD/!x86 (pkubaj)
0f4fddc Add also ifdef __x86_64__ (pkubaj)
|
| | | | | |
|
| | | |/
| |/|
| | | |
Checking battery status uses x86-only headers and functions. Remove this functionality to get it to build on other architectures.
|
| |\ \ \
| |/ /
|/| |
| | | |
3455efa ban peers sending bad pow outright (moneromooo-monero)
|
| | | |
| | |
| | |
| | | |
PoW is expensive to verify, so be strict
|
| |\ \ \
| |_|/
|/| |
| | | |
8330e77 monerod can now sync from pruned blocks (moneromooo-monero)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the peer (whether pruned or not itself) supports sending pruned blocks
to syncing nodes, the pruned version will be sent along with the hash
of the pruned data and the block weight. The original tx hashes can be
reconstructed from the pruned txes and theur prunable data hash. Those
hashes and the block weights are hashes and checked against the set of
precompiled hashes, ensuring the data we received is the original data.
It is currently not possible to use this system when not using the set
of precompiled hashes, since block weights can not otherwise be checked
for validity.
This is off by default for now, and is enabled by --sync-pruned-blocks
|
| | |/
|/|
| |
| | |
Support RandomX PoW algorithm
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
2cd4fd8 Changed the use of boost:value_initialized for C++ list initializer (JesusRami)
4ad191f Removed unused boost/value_init header (whyamiroot)
928f4be Make null hash constants constexpr (whyamiroot)
|
| | | |
| | |
| | |
| | | |
Simplify m_template initialization in miner
|
| | | | |
|
| | | | |
|
| | |/
|/|
| |
| | |
So it can be used by others without encumbrance
|
| |/ |
|
| | |
|
| |\
| |
| |
| | |
bcd2da7 miner: fix --bg-mining-enable description (moneromooo-monero)
|
| | | |
|
| |\ \
| |/
|/|
| | |
df83ed7 consensus: from v12, enforce >= 2 outputs (moneromooo-monero)
|
| | | |
|
| | |
| |
| |
| | |
just in case
|
| | | |
|
| | |
| |
| |
| | |
issue: #5568
|
| | | |
|
| |/ |
|
| |\
| |
| |
| | |
6643b047 Increment m_threads_active when mining thread starts (Doyle)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
07dd5536 hardfork: remove "no hf version db" recreation check (moneromooo-monero)
|
| | |/
| |
| |
| |
| | |
This is now obsolete, and this removes the warning on startup
on a new db that confuses some people
|
| |\ \
| | |
| | |
| | | |
5e673c03 blockchain_db: fix db txn ending too early (moneromooo-monero)
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The db txn in add_block ending caused the entire overarching
batch txn to stop.
Also add a new guard class so a db txn can be stopped in the
face of exceptions.
Also use a read only db txn in init when the db itself is
read only, and do not save the max tx size in that case.
|
| |\ \
| |/
|/|
| | |
cbf32241 rpc: make wide_difficulty hexadecimal (moneromooo-monero)
|
| | |
| |
| |
| | |
This should be friendlier for clients which don't have bignum support
|
| | |
| |
| |
| |
| | |
Related to emission, reorgs, getting tx data back, output
distribution and histogram
|
| |\ \
| | |
| | |
| | | |
def40161 miner: fix race when stopping mining with start mining enabled (moneromooo-monero)
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
113e4877 blockchain_stats: fix sign in formatting function (moneromooo-monero)
adaea3ea various: remove unused variables (moneromooo-monero)
631ef00e blockchain: some debug info when adding txes-from-block fails (moneromooo-monero)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
a2561653 wallet: new option to start background mining (moneromooo-monero)
|
| | |/
| |
| |
| |
| |
| | |
The setup-background-mining option can be used to select
background mining when a wallet loads. The user will be asked
the first time the wallet is created.
|
| |\ \
| | |
| | |
| | | |
089c7637 cryptonote: rework block blob size sanity check (moneromooo-monero)
|
| | |/
| |
| |
| |
| | |
Use the actual block weight limit, assuming that weight is always
greater or equal to size
|
| |\ \
| |/
|/|
| |
| |
| |
| |
| |
| | |
c84ea299 cryptonote_basic: some more minor speedups (moneromooo-monero)
e40eb2ad cryptonote_basic: speedup calculate_block_hash (moneromooo-monero)
547a9708 cryptonote: block parsing + hash calculation speedup (moneromooo-monero)
11604b6d blockchain: avoid unneeded block copy (moneromooo-monero)
8461df04 save some database calls when getting top block hash and height (moneromooo-monero)
3bbc3661 Avoid repeated (de)serialization when syncing (moneromooo-monero)
|
| | | |
|
| | |
| |
| |
| |
| | |
The block 202612 fix can be left tested at the end, if we
already know we're not in the general case
|
