Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore FIRST_CLASS_MESSAGING #2014

Closed
wants to merge 1 commit into from
Closed

Conversation

luke-jr
Copy link
Member

@luke-jr luke-jr commented Nov 15, 2012

No description provided.

@Diapolo
Copy link

Diapolo commented Nov 15, 2012

NACK

@laanwj
Copy link
Member

laanwj commented Nov 17, 2012

We had this discussion many times before, this is just not coming back

@BitcoinPullTester
Copy link

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/d0c637aecbd19506846f35e21b446e856a5e6ab5 for binaries and test log.

@luke-jr luke-jr closed this Nov 25, 2012
HashUnlimited pushed a commit to chaincoin/chaincoin that referenced this pull request Apr 6, 2018
* Allow disabling txindex in lite mode

* Do not load/store Dash-specific cache in lite mode

* Do not create/show masternode tab in lite mode

* Do not connect PS actions in lite mode

* Fix sync/ignore block updates in Dash submodules in lite mode

Conflicts:
	src/init.cpp
KolbyML pushed a commit to KolbyML/bitcoin that referenced this pull request Dec 5, 2020
…recipient is shielded

daa5d7f Test: add coverage for sendmany + shield address (random-zebra)
13ddf93 RPC: Document shielded recipients in sendmany help (random-zebra)
8ecf222 [Wallet] Spend from delegations added to SaplingOperation (random-zebra)
267ae07 [RPC] Redirect sendmany to 'shieldedsendmany "from_transparent"' (random-zebra)
40b6f7e BUG: fix spending of P2CS in RPC sendmany (random-zebra)

Pull request description:

  Instead of throwing an error, let's repack the json request and send it to `shieldedsendmany`.
  This makes the integration of send-to-shield-address much easier for third-party services.

  We keep the old implementation of `sendmany` for `t->t` transactions, until the two flows are properly abstracted.

  Also fix a minor bug found in `sendmany` (not properly considering the `fIncludeDelegated` flag), and add capability to spend P2CS inside `SaplingOperation`.

  Note:  the same thing proposed here, could be done with the RPC `sendtoaddress` (future).

ACKs for top commit:
  furszy:
    Nice, utACK daa5d7f . More than ready to get merged then :)
  Fuzzbawls:
    utACK daa5d7f

Tree-SHA512: 8ecf996687cab5236c95ceaa8be5dfee660e3c984e00c005b75731103bfe8354719a7f9c91ab70665b8d0149bd52dbe222bd1ec9b845ab50587286b89028044c
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants