I could use a tiny amount to aid in registering my account:

BTSX5FP5WeyoY24EGMfs65Tvevv3aq53b4g5fNG78HLnU5MBaAeExi

Thanks!

Quote from: bytemaster on March 01, 2014, 09:19:24 PM

Quote from: Kyune on March 01, 2014, 09:18:03 PM

Quote from: bytemaster on February 28, 2014, 01:00:38 AM
We cannot make any promises of allocation; however, we theorize that market forces will conspire to honor recommendations we make even in the extreme case of our team being killed in a plane crash and someone else is left to finish the software.

Could you (or anyone else) explain a little more about the reasoning behind the bolded statement (emphasis added), or point me to a document where you have already explained it?  I'm trying to understand why, in theory, economic forces would enforce this "social contract" even with respect to third-party DACs.  I'm guessing someone has already written about this elsewhere, but I'm having trouble finding it.

https://bitsharestalk.org/index.php?topic=2876.0

Thank you.

At first glance I don't fully agree with all the assertions made therein, but the link gives me a good starting point for thinking about it.

Quote from: bytemaster on February 28, 2014, 01:00:38 AM
We cannot make any promises of allocation; however, we theorize that market forces will conspire to honor recommendations we make even in the extreme case of our team being killed in a plane crash and someone else is left to finish the software.

Could you (or anyone else) explain a little more about the reasoning behind the bolded statement (emphasis added), or point me to a document where you have already explained it?  I'm trying to understand why, in theory, economic forces would enforce this "social contract" even with respect to third-party DACs.  I'm guessing someone has already written about this elsewhere, but I'm having trouble finding it.

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.

The slow confirmation times appear to be the result of one or more miners having adopted a policy of refusing to include more than one transaction per block.  See here:

http://btsblock.com/chain/ProtoShares

Ypool (the largest pool) appears to be one the bad actors.  If you compare block numbers from their stats page to the blockchain explorer, it looks like all of ypool's blocks are only including 1 transaction at most.

Thus, everyone trying to send PTS through the network is having to wait until someone else (such as the beeeeer pool) find a block, at which point a bunch of transactions finally get included in a block.

I'm interested.