Main Menu

The YPool miner doesn't accept transactions?

Started by skaffen, November 18, 2013, 09:57:01 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

testz

#5
I found another pool which produces blocks and doesn't accept transactions, it's http://54.238.185.113 (pts.rpool.net)

Pool owner, please fix it ASAP, probably your miners use old ypool miner which has this problem.

You can look for a blocks produced by your pool http://54.238.185.113/blocks and compare to information from block explorer http://ptsexplorer.cloudapp.net/chain/BitShares-PTS

We have one more pool which does the same.

andhar

#4
http://bitsharestalk.org/index.php?topic=449.330

Seems like he's getting his miners to upgrade with a new version.

Hope this fixes it.
[url="https://steemit.com/@harand"]https://steemit.com/@harand[/url]

GurungBoi

PTS : PYoeV73D2VsY8HQYmHXECoFUksoxzW9vxA     BTC :18FMQ4jA98JwosE5AMAuyDCH1JSLXS41nc  LTC :LPKCvG4VSFvxM4gsWxe6cCsqSJZ7q6V5BF

Tip/Donate if you feel I helped you u in some way.

andhar

Seems like he's working on a fix. No update since Reply #15 on: November 17, 2013, 02:41:51 PM ยป do'h.

http://bitsharestalk.org/index.php?topic=740.msg8222#msg8222
[url="https://steemit.com/@harand"]https://steemit.com/@harand[/url]

skaffen

As far as I understand, from below, the ypool miner isn't confirming any transactions.  Their blocks always have only 1 transaction! That's pretty harmful to the network, isn't it?  Are there any ways to counter this anti-social behaviour?

Quote from: jh00 on November 17, 2013, 08:18:32 PM
Quote from: Kyune on November 17, 2013, 07:37:56 PM
Ypool appears to have adopted a policy of including a maximum of one transaction per block, which appears to be slowing down transaction confirmations on the network.  Compare the ypool stats page to the list of 1-transaction blocks on

http://btsblock.com/chain/ProtoShares

Several people have noticed that transactions are getting held up with 0 confirmations (with or without transactions fees) as numerous blocks roll by until a different pool finds a block, at which a bunch of transactions finally get their first confirmation.

This seems harmful to the network as a whole.
See my post here
There is no evil intention, just a lack of time on my side.
MMC: MLh27rbqmDWr6w9V5rWDV6pUFjganJhZv3
PTS:  Pf53gFMhCToW2nGovRKfRc4tWoXBY1A3Pq