Weekly Update #141

Sunny_King · May 6, 2015, 5:14am

[ul][li]Emeth has updated latest peermessage/peerapp project to run against peercoin master (to become v0.5): https://www.peercointalk.org/index.php?topic=4102[/li]
[li]Current peercoin protocol does not allow outputs with value < 0.01PPC, to discourage dust problem. This also prevents the zero amount on outputs, unlike bitcoin. To fully support OP_RETURN, from v0.5 on, zero output amount will be allowed, but nonzero amount less than 0.01PPC is still not allowed.[/li]
[li]v0.5 release will be mandatory upgrade, with a 2 month upgrade window. Once testing completes on the protocol change, I will announce a release schedule.[/li][/ul]

Have fun!

peerchemist · May 6, 2015, 8:50am

Will 0.5 merge new version of Bitcoin core?

mably · May 6, 2015, 9:03am

Where can we get the final version 0.5 code so we can update the ppcsuite project accordingly ?

I’m mainly thinking about the preprogrammed long range attack security fix.

Thireus · May 6, 2015, 10:47am

[quote=“mably, post:3, topic:3495”]Where can we get the final version 0.5 code so we can update the ppcsuite project accordingly ?

I’m mainly thinking about the preprogrammed long range attack security fix.[/quote]

Same here, I’ll have to adjust the apps I’m developping mainly because of this zero output amount.

mably · May 6, 2015, 11:36am

Is this rule enforced at the protocol level? If yes, could someone give us a link to the corresponding ppcoin code?

I have only found some wallet related code at the moment:

github.com

peercoin/peercoin/blob/v0.4.0ppc/src/qt/walletmodel.cpp#L100


      
          
          // Pre-check input data for validity
          foreach(const SendCoinsRecipient &rcp, recipients)
          {
              if(!validateAddress(rcp.address))
              {
                  return InvalidAddress;
              }
              setAddress.insert(rcp.address);
          
              if(rcp.amount < MIN_TXOUT_AMOUNT)
              {
                  return InvalidAmount;
              }
              total += rcp.amount;
          }
          
          if(recipients.size() > setAddress.size())
          {
              return DuplicateAddress;
          }

Thanx for your help.

thehuntergames · May 6, 2015, 4:13pm

me three, I want to know what was changed wrt long range attack

Had a quick glance, all I see are OP_Return related changes, but no kernel stuff wrt minting stakes

mhps · May 7, 2015, 1:59am

I think for this kind of change the course of action is 1) propose a solution in the forum for comments 2) implement and test 3) release

We are not in 1) yet.

The long range attack takes time to happen because it is long range. I agree it should be put on agenda.

sigmike · May 9, 2015, 8:14am

Is this rule enforced at the protocol level? If yes, could someone give us a link to the corresponding ppcoin code?[/quote]

Yes, here: https://github.com/ppcoin/ppcoin/blob/v0.4.0ppc/src/main.cpp#L464

mably · May 9, 2015, 8:18am

Is this rule enforced at the protocol level? If yes, could someone give us a link to the corresponding ppcoin code?[/quote]

Yes, here: https://github.com/ppcoin/ppcoin/blob/v0.4.0ppc/src/main.cpp#L464[/quote]

Thanx for the link sigmike.

In fact kac- had it implemented in ppcd here: https://github.com/ppcsuite/ppcd/blob/master/blockchain/ppc.go#L608

EDIT: created a related wiki page: https://wiki.peercointalk.org/index.php?title=CTransaction%3A%3ACheckTransaction