Bitcoin Forum
April 03, 2020, 07:04:37 AM *
News: Latest Bitcoin Core release: 0.19.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: [ATTN POOL OPS] List of pools' transaction policies.  (Read 3266 times)
kinlo
Sr. Member
****
Offline Offline

Activity: 263
Merit: 250


Pool operator of Triplemining.com


View Profile
March 15, 2013, 04:43:45 PM
 #21

Triplemining currently does everything with default settings from the 0.7.2 client.  So no filtering, 250kb blocks etc etc
At least for now, I'm waiting for 0.8.1 before I start playing again with the values
1585897477
Hero Member
*
Offline Offline

Posts: 1585897477

View Profile Personal Message (Offline)

Ignore
1585897477
Reply with quote  #2

1585897477
Report to moderator
1585897477
Hero Member
*
Offline Offline

Posts: 1585897477

View Profile Personal Message (Offline)

Ignore
1585897477
Reply with quote  #2

1585897477
Report to moderator
1585897477
Hero Member
*
Offline Offline

Posts: 1585897477

View Profile Personal Message (Offline)

Ignore
1585897477
Reply with quote  #2

1585897477
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1585897477
Hero Member
*
Offline Offline

Posts: 1585897477

View Profile Personal Message (Offline)

Ignore
1585897477
Reply with quote  #2

1585897477
Report to moderator
1585897477
Hero Member
*
Offline Offline

Posts: 1585897477

View Profile Personal Message (Offline)

Ignore
1585897477
Reply with quote  #2

1585897477
Report to moderator
grue
Legendary
*
Offline Offline

Activity: 2058
Merit: 1209



View Profile
March 15, 2013, 04:48:38 PM
Last edit: March 15, 2013, 10:34:34 PM by grue
 #22

No:
  • This is biased to support SatoshiDice's DDoS attack against Bitcoin. Instead of "transaction discrimination", it should be "anti-flooding filter quality"
agreed, "discrimination" has a negative connotation to it.

change it to "transaction filtering" or "ignored transactions"

It is pitch black. You are likely to be eaten by a grue.

Adblock for annoying signature ads | Enhanced Merit UI
doublec
Legendary
*
Offline Offline

Activity: 1078
Merit: 1000


View Profile
March 15, 2013, 10:17:29 PM
 #23

Bitparking is currently using all the default settings from the 0.7.2 client.
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 2058
Merit: 1007


Poor impulse control.


View Profile WWW
March 16, 2013, 12:57:04 AM
 #24

No:
  • This is biased to support SatoshiDice's DDoS attack against Bitcoin. Instead of "transaction discrimination", it should be "anti-flooding filter quality"
agreed, "discrimination" has a negative connotation to it.

change it to "transaction filtering" or "ignored transactions"

Fixed. I was getting around to doing it, then that stupid Berkeley database ruined everything and I forgot.

Bitparking is currently using all the default settings from the 0.7.2 client.

Thanks, doublec.

I'm not planning on updating the OP until there's a patch or there's no bdb clients left - until then block sizes will be limited to default for pretty much everyone. Although I suppose I could keep the "tx filtering" updated.

Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
Graet
VIP
Legendary
*
Offline Offline

Activity: 980
Merit: 1000



View Profile WWW
March 16, 2013, 04:25:19 AM
 #25

No:
  • This is biased to support SatoshiDice's DDoS attack against Bitcoin. Instead of "transaction discrimination", it should be "anti-flooding filter quality"
agreed, "discrimination" has a negative connotation to it.

change it to "transaction filtering" or "ignored transactions"

Fixed. I was getting around to doing it, then that stupid Berkeley database ruined everything and I forgot.

Bitparking is currently using all the default settings from the 0.7.2 client.

Thanks, doublec.

I'm not planning on updating the OP until there's a patch or there's no bdb clients left - until then block sizes will be limited to default for pretty much everyone. Although I suppose I could keep the "tx filtering" updated.
Looks like not all pools are on the defaults despite all that has happened this week Sad
http://blockchain.info/block-index/358797/00000000000001ba4bd010816667d2706fc0ddb3b258835c7d40d2a8c4d2b6a9
617kB from HHTT


| Ozcoin Pooled Mining Pty Ltd https://ozcoin.net Double Geometric Reward System https://lc.ozcoin.net for Litecoin mining DGM| https://crowncloud.net VPS and Dedicated Servers for the BTC community
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 2058
Merit: 1007


Poor impulse control.


View Profile WWW
March 16, 2013, 04:32:28 AM
 #26

No:
  • This is biased to support SatoshiDice's DDoS attack against Bitcoin. Instead of "transaction discrimination", it should be "anti-flooding filter quality"
agreed, "discrimination" has a negative connotation to it.

change it to "transaction filtering" or "ignored transactions"

Fixed. I was getting around to doing it, then that stupid Berkeley database ruined everything and I forgot.

Bitparking is currently using all the default settings from the 0.7.2 client.

Thanks, doublec.

I'm not planning on updating the OP until there's a patch or there's no bdb clients left - until then block sizes will be limited to default for pretty much everyone. Although I suppose I could keep the "tx filtering" updated.
Looks like not all pools are on the defaults despite all that has happened this week Sad
http://blockchain.info/block-index/358797/00000000000001ba4bd010816667d2706fc0ddb3b258835c7d40d2a8c4d2b6a9
617kB from HHTT

HHTT has figured out bdb's limits, and is using those?

Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
doublec
Legendary
*
Offline Offline

Activity: 1078
Merit: 1000


View Profile
March 16, 2013, 04:55:01 AM
 #27

HHTT has figured out bdb's limits, and is using those?
They might be doing what I'm doing. My 0.8.0 stratum server node is connected behind a 0.7.2 node so if it sends a bad block the 0.7.2 node will stop it before propagating it to the network. My stratum server is at the defaults though since I'd rather not orphan a block and halt my 0.7.2 getwork node.
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 2058
Merit: 1007


Poor impulse control.


View Profile WWW
March 16, 2013, 05:40:07 AM
 #28

HHTT has figured out bdb's limits, and is using those?
They might be doing what I'm doing. My 0.8.0 stratum server node is connected behind a 0.7.2 node so if it sends a bad block the 0.7.2 node will stop it before propagating it to the network. My stratum server is at the defaults though since I'd rather not orphan a block and halt my 0.7.2 getwork node.

If fireduck is doing what you are but with the 0.8.0 server at accepting larger blocks, he will want to fix that fast - a PPS pool does not want orphans.

Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
miernik
Sr. Member
****
Offline Offline

Activity: 334
Merit: 250


View Profile WWW
June 04, 2013, 12:33:26 PM
 #29

Now that 0.8.2 is out, perhaps pool operators can start updating the list, especially that the default minimum low-priority fee in pre-0.8.2 is 0.0005 BTC/kB and from 0.8.2 is 0.0001 BTC/kB, so its quite important to see which pools use which policies.

Luke-Jr
Legendary
*
Offline Offline

Activity: 2506
Merit: 1022



View Profile
June 04, 2013, 05:53:54 PM
 #30

Now that 0.8.2 is out, perhaps pool operators can start updating the list, especially that the default minimum low-priority fee in pre-0.8.2 is 0.0005 BTC/kB and from 0.8.2 is 0.0001 BTC/kB, so its quite important to see which pools use which policies.
Not quite. I'm pretty sure the 0.0005 BTC was only for sending fees.
The reason behind reducing it was that miners were already accepting the lower fees anyway.

Pages: « 1 [2]  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!