| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
This is intended to catch traffic coming from a web browser,
so we avoid issues with a web page sending a transfer RPC to
the wallet. Requiring a particular user agent can act as a
simple password scheme, while we wait for 0MQ and proper
authentication to be merged.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Keep the immediate direct deps at the library that depends on them,
declare deps as PUBLIC so that targets that link against that library
get the library's deps as transitive deps.
Break dep cycle between blockchain_db <-> crytonote_core.
No code refactoring, just hide cycle from cmake so that
it doesn't complain (cycles are allowed only between
static libs, not shared libs).
This is in preparation for supproting BUILD_SHARED_LIBS cmake
built-in option for building internal libs as shared.
|
| | |
|
| |
|
|
|
|
|
|
| |
This plugs a privacy leak, where the wallet tells the daemon
which transactions contain outputs for the wallet by asking
for additional information for that particular transaction.
As a nice bonus, this actually makes refresh slightly faster.
|
| | |
|
| |
|
|
|
| |
It is not yet constrained to a fork, so don't use on the real network
or you'll be orphaned or rejected.
|
| |
|
|
| |
to get random ringct outputs to mix with
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This plugs a privacy leak from the wallet to the daemon,
as the daemon could previously see what input is included
as a transaction input, which the daemon hadn't previously
supplied. Now, the wallet requests a particular set of
outputs, including the real one.
This can result in transactions that can't be accepted if
the wallet happens to select too many outputs with non standard
unlock times. The daemon could know this and select another
output, but the wallet is blind to it. It's currently very
unlikely since I don't think anything uses non default
unlock times. The wallet requests more outputs than necessary
so it can use spares if any of the returns outputs are still
locked. If there are not enough spares to reach the desired
mixin, the transaction will fail.
|
| |
|
|
|
|
|
|
| |
This constrains the number of instances of any amount
to the unlocked ones (as defined by the default unlock time
setting: outputs with non default unlock time are not
considered, so may be counted as unlocked even if they are
not actually unlocked).
|
| | |
|
| |\
| |
| |
| | |
014f3a0 Add a daemon RPC version, and make simplewallet check it (moneromooo-monero)
|
| | |
| |
| |
| |
| | |
If the version is different, simplewallet will refuse to use that
daemon, unless --allow-mismatched-daemon-version is used.
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
restricted mode.
|
| |
|
|
|
|
|
| |
When m_refresh_from_block_height has been set, only hashes will be
retrieved up to that height, instead of full blocks. The same will
be done for "refresh <height>" when the specified height is beyond
the current local blockchain.
|
| |\
| |
| |
| |
| | |
d662ab5 rpc: print human readable time since received when printing pool (moneromooo-monero)
5c9dd23 rpc: add a do_not_relay boolean to tx submission (moneromooo-monero)
|
| | |
| |
| |
| | |
Just to make it easier
|
| |/ |
|
| |\
| |
| |
| | |
8757e46 add blockhashing blob to getblocktemplate (Howard Chu)
|
| | | |
|
| |\ \
| |/
|/|
| | |
24b3e90 Convey tx verification failure reasons to the RPC client (moneromooo-monero)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows appropriate action to be taken, like displaying
the reason to the user.
Do just that in simplewallet, which should help a lot in
determining why users fail to send.
Also make it so a tx which is accepted but not relayed is
seen as a success rather than a failure.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a list of existing output amounts along with the number
of outputs of that amount in the blockchain.
The daemon command takes:
- no parameters: all outputs with at least 3 instances
- one parameter: all outputs with at least that many instances
- two parameters: all outputs within that many instances
The default starts at 3 to avoid massive spamming of all dust
outputs in the blockchain, and is the current minimum mixin
requirement.
An optional vector of amounts may be passed, to request
histogram only for those outputs.
|
| | |
|
| |
|
|
|
|
| |
The blocked ip list will still hold them till next time
a connection attempt is made with that IP, so the effective
length of the ban may be negative.
|
| |
|
|
|
| |
It can flush a particular tx, or the whole pool (the RPC command
can flush a list of transactions too)
|
| | |
|
| |
|
|
|
| |
Some of it uses hardcoded height, which will need some thinking
for next (voted upon) fork.
|
| |
|
|
|
|
|
| |
which fixes the status command via RPC too.
Turns out there are two versions of the GET_INFO call.
I'd never noticed before.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| | |
8ea7af1 Allow the wallet to access hard fork information (moneromooo-monero)
760331b epee: make log macros behave like statements (moneromooo-monero)
3f2970f Add missing semicolons after log statements (moneromooo-monero)
|
| | |
| |
| |
| | |
And make it change behavior slightly when close/after first hard fork
|
| |/
|
|
| |
and add top block hash in get_info RPC
|
| |
|
|
|
|
| |
This fixes coretests, which does not register daemon specific arguments,
but uses core, which uses those arguments. Also gets rid of an unwanted
dependency on daemon code from core.
|
| |\
| |
| |
| | |
7574297 core_rpc_server: add a --restricted-rpc option (moneromooo-monero)
|
| | |
| |
| |
| |
| | |
It does not expose the RPC for commands like start_mining, etc
(ie, commands a public node operator might want to be restricted)
|
| |\ \
| | |
| | |
| | | |
55e5a33 rpc: pass current block target in rpc (moneromooo-monero)
|
| | |/
| |
| |
| |
| | |
This fixes the hash rate being wrong on testnet after the switch
to 2 minute blocks
|
| |/ |
|
| |
|
|
|
|
|
|
| |
The last relayed time of a transaction is maintained, and
transactions will be relayed again if they are still in the
pool after a certain amount of time, which increases with
the transaction's age. All such transactions are resent,
whether or not they originated on the local node.
|
| |
|
|
|
|
|
| |
They check whether they're running on testnet by accessing the
m_rpc_server object, which does not exist when in RPC mode.
Also, fix hard_fork_info being called with the wrong API.
|
| |
|
|
| |
I had never tested it, obviously
|
| | |
|
| | |
|