Skip to content

Conversation

TheBlueMatt
Copy link
Contributor

@luke-jr
Copy link
Member

luke-jr commented Jul 1, 2012

ACK

@gmaxwell
Copy link
Contributor

gmaxwell commented Jul 1, 2012

Has someone tried syncing a node connect=ed to a peer running this?

@TheBlueMatt
Copy link
Contributor Author

Yes, works.

jgarzik pushed a commit that referenced this pull request Jul 2, 2012
@jgarzik jgarzik merged commit da1103f into bitcoin:master Jul 2, 2012
coblee pushed a commit to litecoin-project/litecoin that referenced this pull request Jul 17, 2012
jwrb pushed a commit to jwrb/paycoin that referenced this pull request Sep 16, 2015
Change send buffer default to 1M, as the send buffer is more often maxed now.
Taken from #[1545](bitcoin/bitcoin#1545) on bitcoin
jwrb pushed a commit to jwrb/paycoin that referenced this pull request Sep 17, 2015
Decrease default send/revieve buffer from 10MB to 1MB as this patch makes it easy for a node to fill both instead of only send.
Ported from [pull 973](bitcoin/bitcoin#973) and [pull 1545](bitcoin/bitcoin#1545)

The largest advantage is not having to read from disk or serialize blocks on getblocks requests.
jwrb pushed a commit to jwrb/paycoin that referenced this pull request Oct 22, 2015
Decrease default send/revieve buffer from 10MB to 1MB as this patch makes it easy for a node to fill both instead of only send.
Ported from [pull 973](bitcoin/bitcoin#973) and [pull 1545](bitcoin/bitcoin#1545)

The largest advantage is not having to read from disk or serialize blocks on getblocks requests.
jwrb pushed a commit to jwrb/paycoin that referenced this pull request Oct 22, 2015
Decrease default send/revieve buffer from 10MB to 1MB as this patch makes it easy for a node to fill both instead of only send.
Ported from [pull 973](bitcoin/bitcoin#973) and [pull 1545](bitcoin/bitcoin#1545)

The largest advantage is not having to read from disk or serialize blocks on getblocks requests.
suprnurd pushed a commit to chaincoin-legacy/chaincoin that referenced this pull request Dec 5, 2017
…elay is enabled in `getnetwork` (bitcoin#1545)

* net: Add fRelayTxes flag

Add a fRelayTxes to keep track of the relay transaction flag
we send to other peers.

* rpc: Add `relaytxes` flag to `getnetworkinfo`

Re-work of PR bitcoin#7841 by dragongem45.
Closes bitcoin#7771.
lateminer pushed a commit to lateminer/bitcoin that referenced this pull request May 6, 2020
de45ddc [GUI] MnWizard: validate IP (random-zebra)
0e3c18f [GUI][Bug] MnWizard: Fix validators for masternode alias and port (random-zebra)

Pull request description:

  First commit fixes the masternode alias: right now only letters and digits are allowed, but special characters (except spaces and hash marks) should be allowed too. It also replaces deprecated `QRegExp` with `QRegularExpression` (as per bitcoin#1124) and fixes the port number to the default.
  Closes bitcoin#1471

  Second commit introduces validation for masternode IP addresses: they should be valid IPv4, IPv6 or .onion addresses and, if not on regtest, they should be reachable and routable. A unit test for the new `validateMasternodeIP` function is added to netbase_tests.
  Also removes the validation for the port, since it's fixed to network-default.

ACKs for top commit:
  Fuzzbawls:
    ACK de45ddc
  furszy:
    ACK de45ddc

Tree-SHA512: f9479483e4d41b80b83b4ca5cd57912dc027e020b92034090e9e1d01a1486696d70ce2fc3cf7253c18cdfcda273f5e203929a3e240f9d3d660b110c3bd009ef8
@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.

'send buffer full' massive log spam
4 participants