Bitcoin Forum
November 07, 2024, 07:36:34 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 [11] 12 13 14 15 »  All
  Print  
Author Topic: [~32 TH] HHTT - Selected Diff/Stratum/PPLNS/Paid Stales/High Availability/Tor  (Read 29785 times)
Wave
Member
**
Offline Offline

Activity: 105
Merit: 10


View Profile
November 07, 2013, 12:30:28 PM
 #201

We are doing great, keep it up gents!
RoadTrain
Legendary
*
Offline Offline

Activity: 1386
Merit: 1009


View Profile
November 07, 2013, 11:04:47 PM
 #202

Can't see the pool URL in the first post? Smiley
Would be great to have it there.
spiccioli (OP)
Legendary
*
Offline Offline

Activity: 1379
Merit: 1003

nec sine labore


View Profile
November 08, 2013, 03:51:19 PM
 #203

Can't see the pool URL in the first post? Smiley
Would be great to have it there.

Gosh... you're right!

I've added a couple of links... Smiley

spiccioli
RoboCoder
Sr. Member
****
Offline Offline

Activity: 388
Merit: 250


Save A Life, Adopt a Pet Today!


View Profile WWW
November 08, 2013, 08:21:35 PM
 #204

I like your model.  I am going to point some hashpower your way to test it out!
RoadTrain
Legendary
*
Offline Offline

Activity: 1386
Merit: 1009


View Profile
November 09, 2013, 10:16:00 AM
 #205

Congrats to someone
https://blockchain.info/block-index/438763/00000000000000018914e17bd674c5d8069ce463e00750cb838b91d3b0ac80c3
spiccioli (OP)
Legendary
*
Offline Offline

Activity: 1379
Merit: 1003

nec sine labore


View Profile
November 09, 2013, 10:20:04 AM
 #206


Woooww!

I need to put a link on it on the OP Smiley

spiccioli
fireduck
Sr. Member
****
Offline Offline

Activity: 392
Merit: 251



View Profile
November 09, 2013, 03:51:25 PM
 #207


Transaction is:
https://blockchain.info/tx/8e9adefd0608b4525d2d35e80247911516d2afcfee8d6bb121c63197ef275df0?show_adv=true

with 18.7908 BTC fee.

I wonder if it was a poorly constructed transaction by hand or a wonky fee calculator (that transaction is indeed huge).

Bitrated user: fireduck.
RoadTrain
Legendary
*
Offline Offline

Activity: 1386
Merit: 1009


View Profile
November 10, 2013, 12:54:39 AM
 #208


Transaction is:
https://blockchain.info/tx/8e9adefd0608b4525d2d35e80247911516d2afcfee8d6bb121c63197ef275df0?show_adv=true

with 18.7908 BTC fee.

I wonder if it was a poorly constructed transaction by hand or a wonky fee calculator (that transaction is indeed huge).

It's not the first tx of this kind.
Seems like those fees are intentional.
jbutter
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
November 14, 2013, 08:50:06 AM
 #209

It's been a little dry lately, come on lucky blocks, where you hiding?
spiccioli (OP)
Legendary
*
Offline Offline

Activity: 1379
Merit: 1003

nec sine labore


View Profile
November 14, 2013, 01:23:08 PM
 #210

It's been a little dry lately, come on lucky blocks, where you hiding?

Lucky periods, per definition, last a lot less than unlucky ones... you can see a lucky period as a reward for enduring an unlucky one Smiley

spiccioli
spiccioli (OP)
Legendary
*
Offline Offline

Activity: 1379
Merit: 1003

nec sine labore


View Profile
November 16, 2013, 01:06:58 PM
 #211

Here we go again!

1bush8 gets 0.27 per block (more or less) and today solving latest block he/she got a nice 0.36 prize!

HHTT is the only pool doing this kind of lottery Smiley

spiccioli
Carlton Banks
Legendary
*
Offline Offline

Activity: 3430
Merit: 3080



View Profile
November 16, 2013, 08:59:00 PM
 #212


Support the discouraging of address re-use.



The exchange rate value of everyone's Bitcoins depends on killing the lists. Including you, me, spiccioli, and everyone mining, pooled, decentrally or solo.

spiccioli, please consider using the address re-use de-prioritising mining node. This will be a step along the way to preventing the public blockchain record from being used against us to devalue our Bitcoins.

Everyone at HHTT should familiarise themselves with the forthcoming HD wallets feature, keychains. You can create as many keychains as you wish, just like single addresses. This will let you lock reward payments to a sequence of crytographically determined keychain addresses instead of one address. It is a superior alternative to locking to a static address, you can gain more privacy with the same level of security.

HD wallets will likely be available in the 0.9 Bitcoin client.


Support the discouraging of address re-use.

Vires in numeris
fireduck
Sr. Member
****
Offline Offline

Activity: 392
Merit: 251



View Profile
November 18, 2013, 07:17:32 PM
 #213


Support the discouraging of address re-use.



The exchange rate value of everyone's Bitcoins depends on killing the lists. Including you, me, spiccioli, and everyone mining, pooled, decentrally or solo.

spiccioli, please consider using the address re-use de-prioritising mining node. This will be a step along the way to preventing the public blockchain record from being used against us to devalue our Bitcoins.

Everyone at HHTT should familiarise themselves with the forthcoming HD wallets feature, keychains. You can create as many keychains as you wish, just like single addresses. This will let you lock reward payments to a sequence of crytographically determined keychain addresses instead of one address. It is a superior alternative to locking to a static address, you can gain more privacy with the same level of security.

HD wallets will likely be available in the 0.9 Bitcoin client.


Support the discouraging of address re-use.


So whatever this thread spam is aside, I've been thinking about that.

For example, if someone wanted to give me an electrum master public key, I could send payments for them to unused addresses on that chain.  I'd be glad to support any other deterministic schemes I could find software for.

Example (not implemented, stated as an example):
A person mines with a username of an electrum master public key.  In the suckers list and status pages HHTT would show something like HMAC(mpk, 'hhtt').substring(0, 20).  That way, no one would be able to see the who mpk.  Then when doing a payment, I would find an unused address on that mpk chain and send the payment to that.  I would also stop posting transaction IDs to make it harder to figure out who each miner was in the payment transactions.  Still possible, but hard after the fact.  The transactions would of course still be visible, but not how much each miner was paid and which miner is which.




Bitrated user: fireduck.
Wave
Member
**
Offline Offline

Activity: 105
Merit: 10


View Profile
November 22, 2013, 12:30:59 PM
 #214

Hey gents, on the main mage we show "Orpahans", it should be Orphans.

-Wave
spiccioli (OP)
Legendary
*
Offline Offline

Activity: 1379
Merit: 1003

nec sine labore


View Profile
November 22, 2013, 01:20:23 PM
 #215

Hey gents, on the main mage we show "Orpahans", it should be Orphans.

-Wave

Wave,

it this pool we say orpahans... Wink

spiccioli
fireduck
Sr. Member
****
Offline Offline

Activity: 392
Merit: 251



View Profile
November 24, 2013, 04:48:10 PM
 #216

Hey gents, on the main mage we show "Orpahans", it should be Orphans.

-Wave

Wave,

it this pool we say orpahans... Wink

spiccioli

I guess I couldn't change it now.

Bitrated user: fireduck.
-Redacted-
Hero Member
*****
Offline Offline

Activity: 574
Merit: 501


View Profile
November 25, 2013, 12:15:33 AM
 #217

I like Orpahans.  You should keep it.
spiccioli (OP)
Legendary
*
Offline Offline

Activity: 1379
Merit: 1003

nec sine labore


View Profile
November 26, 2013, 07:45:18 AM
 #218

This is going to hurt...

spiccioli
Wave
Member
**
Offline Offline

Activity: 105
Merit: 10


View Profile
November 26, 2013, 04:45:37 PM
 #219

What is going to hurt?
spiccioli (OP)
Legendary
*
Offline Offline

Activity: 1379
Merit: 1003

nec sine labore


View Profile
November 27, 2013, 01:23:38 PM
 #220

What is going to hurt?

Three days without blocks Smiley but we went through...

spiccioli
Pages: « 1 2 3 4 5 6 7 8 9 10 [11] 12 13 14 15 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!