| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |\ \
| | |
| | |
| | | |
e509ede trezor: adapt to new passphrase mechanism (ph4r05)
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| | |
- choice where to enter passphrase is now made on the host
- use wipeable string in the comm stack
- wipe passphrase memory
- protocol optimizations, prepare for new firmware version
- minor fixes and improvements
- tests fixes, HF12 support
|
| |\ \
| | |
| | |
| | | |
b367630 simplewallet : missing function block separator (sumogr)
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | | |
7c4a400 simplewallet: fix strings (show_transfers & export_transfers) (sumogr)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
69b5992 simplewallet: new 'address one-off <major> <minor>' command (moneromooo-monero)
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | | |
927fd47 simplewallet: fix smart mining not starting after first setup (moneromooo-monero)
|
| | | | |
| | | |
| | | |
| | | | |
Also avoid rewriting the wallet if the setting is already was we need
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
c61abf8 remove empty statements (shopglobal)
|
| | |/ / /
| | | |
| | | |
| | | | |
Cleaning up a little around the code base.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The warning about spending more than one output with similar creation
time was skipped if print-ring-members was not set, and it defaults to
false, which means most people probably aren't getting this warning if
they spend correlated outputs.
Reported by SeventhAlpaca.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | | |
0349347e ringdb: use a different iv for key and data in rings table (moneromooo-monero)
7b882087 simplewallet: reword mixin in user message in terms of ring size (moneromooo-monero)
f507a43a wallet2: do not remove known rings when a tx fails (moneromooo-monero)
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
a6c24412 wallet: fix exceptions getting the hash of a pruned tx (moneromooo-monero)
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
a6a2ad6c simplewallet: set manual refresh mode in rescan_bc (moneromooo-monero)
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This ensures we get asked for the password if needed
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
88b82bef simplewallet: point to "set help" in the lock screen message (moneromooo-monero)
f19c9f23 util: allow newlines in string to be split (moneromooo-monero)
|
| | |/ / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
ae84ec90 wallet-cli/rpc: allow sweep_all to use outputs in all subaddresses within an account (stoffu)
|
| | | |/ / /
| |/| | |
| | | | |
| | | | | |
account
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
d93e1dff simplewallet: warn on refresh if refresh-from-block-height seems off (moneromooo-monero)
|
| | | |/ / /
| |/| | | |
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | |
| | | | |
| | | | | |
94266eeb simplewallet: fix output age display with duplicate heights (moneromooo-monero)
f1d379d2 simplewallet: fix "outputs in same tx" detector (moneromooo-monero)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The highlight check was based on height, so would highlight
any output at that height, resulting in several matches if
a fake out was picked at the same height as the real spend
|
| | |/ / /
| | | |
| | | |
| | | |
| | | | |
It was comparing source txids, but txids were empty,
so all checks triggered
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | | |
f812783 simplewallet: fix encrypted payment id note triggering on dummy ones (moneromooo-monero)
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | | |
67b4a19e simplewallet: noob-friendly help menu (wowario)
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
22d30866 simplewallet: add missing inactivity-lock-timeout to set help blurb (moneromooo-monero)
9f57f0df simplewallet: do not mention inactivity if a lock was manual (moneromooo-monero)
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
d64e5aa7 wallet: allow message sign/verify for subaddresses (moneromooo-monero)
|
| | |/ / / |
|
| | | | | |
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | | |
6dec0013 simplewallet: fix restore height warning (selsta)
|
| | | |/
| |/| |
|
| |\ \ \
| |/ /
|/| |
| | | |
9768e96 simplewallet: remove remaining payment id dead code (moneromooo-monero)
|
| | | |
| | |
| | |
| | | |
pointed out by coverity
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As reported by Tramèr et al, timing of refresh requests can be used
to see whether a password was requested (and thus at least one output
received) since this will induce a delay in subsequent calls.
To avoid this, we schedule calls at a given time instead of sleeping
for a set time (which would make delays additive).
To further avoid a scheduled call being during the time in which a
password is prompted, the actual scheduled time is now randomized.
|
| | |/
|/|
| |
| |
| |
| |
| | |
We get new pool txes before processing any tx, pool or not.
This ensures that if we're asked for a password, this does not
cause a measurable delay in the txpool query after the last
block query.
|
| |\ \
| | |
| | |
| | | |
d60c1b6 changed 'batttery' to 'battery' (jakehemmerle)
|
| | |/ |
|
| | |
| |
| |
| | |
Lists nodes exposing their RPC port for public use
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |\
| |
| |
| | |
32d6376 simplewallet: add --restore-from-seed alias (moneromooo-monero)
|
| | |
| |
| |
| | |
It may be more intuitive for some people
|
