Block! by cryptostarusa 
Three blocks while I slept...gotta love it!
This is our 3rd of BLOCK SATURDAY!
Continue sleeping
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 135. (Read 5352229 times)
July 14, 2018, 08:36:26 AM
Three blocks while I slept...gotta love it!
This is our 3rd of BLOCK SATURDAY!
Continue sleeping
July 14, 2018, 08:35:13 AM
Block! by cryptostarusa
Three blocks while I slept...gotta love it!
This is our 3rd of BLOCK SATURDAY!
July 14, 2018, 05:26:27 AM
How I feel waking up to a triple BTClock Morning!!!
July 14, 2018, 04:31:05 AM
Where I can get that Ph/second miners. I have only 1Th/s ASIC bitcoin hashing speed.
July 14, 2018, 02:53:44 AM
Superblocks!!!
Thanks for mining guys!
Finnally reached my full 5N yesterday, so this is very welcome
Thanks for mining guys!
Finnally reached my full 5N yesterday, so this is very welcome
July 14, 2018, 02:42:55 AM
Whooohooo get that dance going for that 4th BTC
BTC July 14, 2018, 02:38:31 AM
WOW waking up to not one not but THREE BTClocks good god this is going to be good weekend....
MINE ON WITH KANO SAN!!!
MINE ON WITH KANO SAN!!!
July 14, 2018, 02:13:44 AM
Block! by cryptostarusa
July 14, 2018, 01:24:18 AM
Block! by 33z
July 14, 2018, 12:45:36 AM
Block! by cryptostarusa again
again July 13, 2018, 10:53:33 PM
segwit transactions are coded in corecoin to be valued at 1/4 the fees of normal transactions.
Actually ... heh - when I looked at that code - it's almost 2 years ago now that they wrote it I think.
I should find that 4 and change it to 1 in our nodes ...
I had to bite, lol.
Would that do anything? aren't the transactions already broadcast with the fee? So making that change wouldn't be able to just grab more fees.
Edit: I'll have to do so more changes to deal with transactions shortly anyway.
Core took out something that only pools would use ... gee I wonder why they would do that?
Something that I've used when blocks were full - to force our payout transaction into the pool work: priority.
So I'l have to do more changes to the transaction selection code anyway and I'll remove the 4x then if possible also.
Wouldn't that negatively affect miner's profits by reducing the fees they get? SegWit gives transactions witness data, and the witness data doesn't count towards the 1 MB block maximum, which was the reasoning behind the 4x value.
I wonder why a decentralised transaction system would consider such a change ... ... ... ... ... ...
Anyway, space vs cost.
You're assuming the result of what I'll change
Hint: I can program better than most of the hackers/idiots in Bitcoin.
July 13, 2018, 10:46:50 PM
segwit transactions are coded in corecoin to be valued at 1/4 the fees of normal transactions.
Actually ... heh - when I looked at that code - it's almost 2 years ago now that they wrote it I think.
I should find that 4 and change it to 1 in our nodes ...
I had to bite, lol.
Would that do anything? aren't the transactions already broadcast with the fee? So making that change wouldn't be able to just grab more fees.
Edit: I'll have to do so more changes to deal with transactions shortly anyway.
Core took out something that only pools would use ... gee I wonder why they would do that?
Something that I've used when blocks were full - to force our payout transaction into the pool work: priority.
So I'l have to do more changes to the transaction selection code anyway and I'll remove the 4x then if possible also.
Wouldn't that negatively affect miner's profits by reducing the fees they get? SegWit gives transactions witness data, and the witness data doesn't count towards the 1 MB block maximum, which was the reasoning behind the 4x value.
July 13, 2018, 07:27:45 PM
segwit transactions are coded in corecoin to be valued at 1/4 the fees of normal transactions.
Actually ... heh - when I looked at that code - it's almost 2 years ago now that they wrote it I think.
I should find that 4 and change it to 1 in our nodes ...
I had to bite, lol.
Would that do anything? aren't the transactions already broadcast with the fee? So making that change wouldn't be able to just grab more fees.
Edit: I'll have to do so more changes to deal with transactions shortly anyway.
Core took out something that only pools would use ... gee I wonder why they would do that?
Something that I've used when blocks were full - to force our payout transaction into the pool work: priority.
So I'l have to do more changes to the transaction selection code anyway and I'll remove the 4x then if possible also.
July 13, 2018, 07:24:05 PM
segwit transactions are coded in corecoin to be valued at 1/4 the fees of normal transactions.
Actually ... heh - when I looked at that code - it's almost 2 years ago now that they wrote it I think.
I should find that 4 and change it to 1 in our nodes ...
I had to bite, lol.
Would that do anything? aren't the transactions already broadcast with the fee? So making that change wouldn't be able to just grab more fees.
July 13, 2018, 07:19:21 PM
Maybe I'm not thinking about all the angles here, but wouldn't this be good if you were the one paying that fee?
I understand it's not good for us miners, but what about the people consolidating these transactions, for example?
There's no trouble consolidating non-segwit transactions.I understand it's not good for us miners, but what about the people consolidating these transactions, for example?
It's 750Kb of a 1.9Mb block - 10500 inputs - for 1sat/Byte
Nope I don't see how that's good at all.
1.7 times the size of a (current) standard block - 1.7 times the data to transmit and store that block ... for 0.0075 BTC
It's someone taking advantage of segwit's and core's anti-non-segwit design.
But it also looks like segwit spam if you look at the transactions.
Edit: So, is it more/less/same expensive for segwit transactions?
Actually ... heh - when I looked at that code - it's almost 2 years ago now that they wrote it I think.
I should find that 4 and change it to 1 in our nodes ...
July 12, 2018, 10:06:51 PM
Maybe I'm not thinking about all the angles here, but wouldn't this be good if you were the one paying that fee?
I understand it's not good for us miners, but what about the people consolidating these transactions, for example?
There's no trouble consolidating non-segwit transactions.I understand it's not good for us miners, but what about the people consolidating these transactions, for example?
It's 750Kb of a 1.9Mb block - 10500 inputs - for 1sat/Byte
Nope I don't see how that's good at all.
1.7 times the size of a (current) standard block - 1.7 times the data to transmit and store that block ... for 0.0075 BTC
It's someone taking advantage of segwit's and core's anti-non-segwit design.
But it also looks like segwit spam if you look at the transactions.
Edit: So, is it more/less/same expensive for segwit transactions?
July 12, 2018, 09:44:39 PM
So anyone notice the evil deeds of segwit today?
That was a 1.9MByte block but only 0.05067870 BTC in fees
There's been a few blocks that size today aroung 1.9Mb or 2Mb
Sux segwit filling up the block chain with crap
I hated segwit right from the start That was a 1.9MByte block but only 0.05067870 BTC in fees
There's been a few blocks that size today aroung 1.9Mb or 2Mb
Sux segwit filling up the block chain with crap
https://btc.com/21555f5a80c49071b57d26f0aee7caae73e4a3f3f4486f664df73489a1989661
Being a total of ~750Kb of the block space
(and about 0.0075 BTC in fees)
I understand it's not good for us miners, but what about the people consolidating these transactions, for example?
It's 750Kb of a 1.9Mb block - 10500 inputs - for 1sat/Byte
Nope I don't see how that's good at all.
1.7 times the size of a (current) standard block - 1.7 times the data to transmit and store that block ... for 0.0075 BTC
It's someone taking advantage of segwit's and core's anti-non-segwit design.
But it also looks like segwit spam if you look at the transactions.
July 12, 2018, 09:42:57 PM
So anyone notice the evil deeds of segwit today?
That was a 1.9MByte block but only 0.05067870 BTC in fees
There's been a few blocks that size today aroung 1.9Mb or 2Mb
Sux segwit filling up the block chain with crap
I hated segwit right from the start That was a 1.9MByte block but only 0.05067870 BTC in fees
There's been a few blocks that size today aroung 1.9Mb or 2Mb
Sux segwit filling up the block chain with crap
https://btc.com/21555f5a80c49071b57d26f0aee7caae73e4a3f3f4486f664df73489a1989661
Being a total of ~750Kb of the block space
(and about 0.0075 BTC in fees)
I understand it's not good for us miners, but what about the people consolidating these transactions, for example?
I see where your logic is but we mine on a pool that gives the transaction fees back to the miners. That is a huge perk of mining here. After each halving it's the transaction fees that help make up the difference so let's cheer and dance for those fees
July 12, 2018, 09:20:06 PM
Ah, miss those pretty Cray YMPs!
pretty close to what is on your phone now. Amazing how technology changes! July 12, 2018, 08:58:49 PM
So anyone notice the evil deeds of segwit today?
That was a 1.9MByte block but only 0.05067870 BTC in fees
There's been a few blocks that size today aroung 1.9Mb or 2Mb
Sux segwit filling up the block chain with crap
I hated segwit right from the start That was a 1.9MByte block but only 0.05067870 BTC in fees
There's been a few blocks that size today aroung 1.9Mb or 2Mb
Sux segwit filling up the block chain with crap
https://btc.com/21555f5a80c49071b57d26f0aee7caae73e4a3f3f4486f664df73489a1989661
Being a total of ~750Kb of the block space
(and about 0.0075 BTC in fees)
I understand it's not good for us miners, but what about the people consolidating these transactions, for example?
Jump to: