Peershares - 1st public alpha test release for Windows and Linux

peersharesd.exe /? >> peershares.txt[/quote]

Thanks. Didn’t think of trying the daemon. So the problem is only with the -qt.

btw I will send you 0.123 shares. Please check in the “overview” pane the undonfirmed amount shows it before getting a green tick in the “transactions”.

Just to let everyone know, there’s an API call list that I started documenting here: https://github.com/Peershares/Peershares/wiki/API-Calls-List

I still have some work to do on this list but the most important stuff is there. I believe you can use all of these commands in the console. Just run the command without the "$ ./peersharesd " in front of it.

peersharesd.exe /? >> peershares.txt[/quote]

Thanks. Didn’t think of trying the daemon. So the problem is only with the -qt.

btw I will send you 0.123 shares. Please check in the “overview” pane the undonfirmed amount shows it before getting a green tick in the “transactions”.[/quote]

That what you were looking for?

we should probably logged that as a bug in the testing subforum.

@pb: thanks man!

[quote=“JohnnyCryptoCoin, post:60, topic:2248”][quote=“jmzeidner, post:56, topic:2248”][quote=“irritant, post:55, topic:2248”][quote=“jmzeidner, post:54, topic:2248”][quote=“Ben, post:53, topic:2248”]

The testing you are looking for is more end user testing of the client/protocol rather than the underlying architecture.

Yup :slight_smile: We’re looking to see if we missed anything (labels, graphics, functionality, controls, etc.), or if during standard usage you’re able to break something. Also, any feedback about how the client works, including areas, functions, or workflows that you think need to be refined is very helpful.[/quote]
so I just received 0.25 shares unexpectedly.

was this a dividend? if so the client does not make that clear.

great job guys. -jmz[/quote]

to me it is clear: the dividends are received in your peercoin client (not peershares), i guess it was to test sending partial shares (0.25), have received them too[/quote]

ah ok, so this won’t really be much of a chore in PeerUnity because the wallets are consolidated… -jmz[/quote]

I sent you another 0.24 of a share :)[/quote]

yep got it! thx.

so are we going to simulate a forking attack here?

-jmz

[quote=“JohnnyCryptoCoin, post:60, topic:2248”][quote=“jmzeidner, post:56, topic:2248”][quote=“irritant, post:55, topic:2248”][quote=“jmzeidner, post:54, topic:2248”][quote=“Ben, post:53, topic:2248”]

The testing you are looking for is more end user testing of the client/protocol rather than the underlying architecture.

Yup :slight_smile: We’re looking to see if we missed anything (labels, graphics, functionality, controls, etc.), or if during standard usage you’re able to break something. Also, any feedback about how the client works, including areas, functions, or workflows that you think need to be refined is very helpful.[/quote]
so I just received 0.25 shares unexpectedly.

was this a dividend? if so the client does not make that clear.

great job guys. -jmz[/quote]

to me it is clear: the dividends are received in your peercoin client (not peershares), i guess it was to test sending partial shares (0.25), have received them too[/quote]

ah ok, so this won’t really be much of a chore in PeerUnity because the wallets are consolidated… -jmz[/quote]

I sent you another 0.24 of a share :)[/quote]

21:08:26

gettransaction 601691254b6cf4a3e05bbca3b442840ea01fb29fb7e662b42c49003775b30074


21:08:26

{
"amount" : 10.00000000,
"confirmations" : 129,
"blockhash" : "ee059a5b0ccc8c6d6a2d627bcba14556b0f5ace6c656a169da55e0d85041f508",
"blockindex" : 2,
"txid" : "601691254b6cf4a3e05bbca3b442840ea01fb29fb7e662b42c49003775b30074",
"time" : 1398115872,
"comment" : "",
"from" : "",
"message" : "",
"to" : "",
"details" : [
{
"account" : "",
"address" : "E9TGHTtCH5MfNtfx6AYg7pE7Gsv1JZLzRQ",
"category" : "receive",
"amount" : 10.00000000
}
]
}

notice that TX is missing a ‘from’ field. Bug?

-jmz

That what you were looking for?
[/quote]

Oh no. I meant when you click on “overview” at the top of the wallet to bring out the overview pane, there is this “Unconfirmed” label with some numbers to its right. Usually the number is 0. I wanted you to check if that number is the amount that I sent you before the shares is confirmed 6 times in your wallet.
I will send you 0.1 again.

It appears to be, nice catch. We’ve been able to replicate the condition and I opened a ticket to address it. Thank you!

I have tried it on peerunity with the faucet. The unconfirmed amount is the received amount before the first confirmation. After the transaction has one confirmation the unconfirmed amount is 0 again. It’s probably intended behavior.

ahh sorry, yes I saw the unconfirmed amount in that field on the overview UI as well, it appears to be working as intended.

[quote=“jmzeidner, post:64, topic:2248”]so are we going to simulate a forking attack here?

-jmz[/quote]

I wouldn’t even know where to begin to start with that, my understanding is that since we have almost 0% Proof of Stake there isn’t much we could do even if we got 51% + of the hashing power.

I think we are just testing basic functionality from an end users perspective.

[quote=“JohnnyCryptoCoin, post:70, topic:2248”][quote=“jmzeidner, post:64, topic:2248”]so are we going to simulate a forking attack here?

-jmz[/quote]

I wouldn’t even know where to begin to start with that, my understanding is that since we have almost 0% Proof of Stake there isn’t much we could do even if we got 51% + of the hashing power.

I think we are just testing basic functionality from an end users perspective.[/quote]

just a reminder, we don’t need any special gear to stage this. We only need the compliance of a subset of the shareholders. 1) write a script for ‘evil behavior’ 2) get the subset of shareholders to run the evil script.

I’m reminded of the Byzantine Generals Problem here. http://research.microsoft.com/en-us/um/people/lamport/pubs/byz.pdf

-jmz

[quote=“masterOfDisaster, post:46, topic:2248”][…]
Ok, after it was stuck for some time it went on. Syncing is very slow, but I’m at block 79917 already (where it seems to be stuck again…)
[…][/quote]

I’m stuck. Can’t get past block 79917. I’m giving a complete new download of the block chain a try…
But maybe there’s something else wrong.

Here’s the getinfo output and the nodes I’m connected to:

"version" : "v0.4.0ppc-beta",
"protocolversion" : 60004,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 70,
"moneysupply" : 586569.52000000,
"connections" : 3,
"proxy" : "",
"ip" : "obfuscated",
"difficulty" : 0.12689515,
"testnet" : true,
"keypoololdest" : 1398232551,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""


"addr" : "74.207.249.18:9903",
"services" : "00000001",
"lastsend" : 1398232122,
"lastrecv" : 1398232123,
"conntime" : 1398229332,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0ppc.rc1-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 83098,
"banscore" : 0
},
{
"addr" : "80.222.122.93:9903",
"services" : "00000001",
"lastsend" : 1398231990,
"lastrecv" : 1398232122,
"conntime" : 1398229338,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0ppc-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 83098,
"banscore" : 0
},
{
"addr" : "76.74.178.237:9903",
"services" : "00000001",
"lastsend" : 1398231630,
"lastrecv" : 1398232121,
"conntime" : 1398229344,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0ppc.rc1-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 83098,
"banscore" : 0
},
{
"addr" : "37.187.75.24:9903",
"services" : "00000001",
"lastsend" : 1398231874,
"lastrecv" : 1398232122,
"conntime" : 1398229367,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0ppc.rc1-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 83098,
"banscore" : 0
},
{
"addr" : "91.121.57.136:9903",
"services" : "00000001",
"lastsend" : 1398231874,
"lastrecv" : 1398232123,
"conntime" : 1398229390,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0ppc.rc1-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 83098,
"banscore" : 0
},
{
"addr" : "85.153.13.35:9903",
"services" : "00000001",
"lastsend" : 1398232087,
"lastrecv" : 1398232087,
"conntime" : 1398229413,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"height" : 82474,
"banscore" : 0
},
{
"addr" : "188.226.187.144:9903",
"services" : "00000001",
"lastsend" : 1398231510,
"lastrecv" : 1398232121,
"conntime" : 1398229415,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0ppc-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 83098,
"banscore" : 0
},
{
"addr" : "23.239.17.57:9903",
"services" : "00000001",
"lastsend" : 1398232111,
"lastrecv" : 1398232112,
"conntime" : 1398229879,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0ppc-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 83099,
"banscore" : 0

Actually we haven’t documented the new command line options yet. I filled an issue here: Add description for new command line options · Issue #113 · Peershares/Peershares · GitHub

@JohnnyCryptoCoin: Here’s my Peershares testnet address, so you can add it to the list when you have a chance.

E9dTY5BHTvqfnXWx1HbNTTdmBuPZzXgm1u

Thanks!

[quote=“masterOfDisaster, post:72, topic:2248”][quote=“masterOfDisaster, post:46, topic:2248”][…]
Ok, after it was stuck for some time it went on. Syncing is very slow, but I’m at block 79917 already (where it seems to be stuck again…)
[…][/quote]

I’m stuck. Can’t get past block 79917. I’m giving a complete new download of the block chain a try…
But maybe there’s something else wrong.[/quote]

This is my command to start peershares

D:\bin\pps\peershares-qt -conf=D:\bin\pps\peershares.conf -datadir=D:\bin\pps -peercoinconf=D:\bin\ppc\ppcoin.conf

I suspect the “.” in your command line may cause problems becuase DOS may have problem with it (even …\ may work) Try absolute path…

Thanks, I’ll try with absolute paths (but doubt that this will help).
The relative path works great when starting ppcoin-qt, the testnet folder gets created and the block chain sync starts. It just gets stuck somewhen.
peershares-qt does completely goes nuts when trying to move the “datadir” (either with absolute or relative path). But that is something different from the Peercoin testnet sync issue I have…
The Peershares testnet block chain syncs perfectly when using the standard datadir.

sent by Tapatalk

[edit]
Deleting Peercoin’s testnet folder content did it. Block chain is synced. I’m proud owner of 10.25 Peershares!
Yeah!
And I could distribute dividends if I had any testnet PPC to spend. But why am I as share holder able to distribute dividends? I mean, I don’t intend to, I’d rather receive some… :wink: But it’s strange that I could if I would want to…
And man, there’s one whale on address E89dzcm4gcsCSmiVgTUCZjZAGCbLzmpvue with 504518.8500 shares! Let me guess - that is the address that belongs to the company/person/institution, which issued the shares, right?
How would I be able to separate these shares in my wallet from those of another Peershares block chain? This is not yet implemented, right?
…I think I should start to read some documentation before I ask questions that are already answered or can be derived from the scope of the current implementation…
[size=14pt]AMAZING![/size]
[/edit]

@JohnnyCryptoCoin: My nick is drduck, not drduke :wink:

Got the 0.25 shares. Why do I receive from unknown?

@masterOfDisaster: Was asking myself the same question, why I am able to distribute shares.

From tomorrow on I will have lots of time to get into Peershares and Peerunity and maybe there
is something more I can test or help with, though I don’t have any special skills. Till now I was
only holding some PPC, but I realized what great things are happening here and what a great
community this is.

That is standard behavior. If the receive address is not in the address book, it is called unknown.

@masterOfDisaster: Was asking myself the same question, why I am able to distribute shares.

It’s not distribute shares. It’s just transfer shares to other people (addresses).

Look forward to testing this out…

Du7MrNDKCaPFxCBRARrngQDjpeHfWJFc9S

@masterOfDisaster: Was asking myself the same question, why I am able to distribute shares.
It's not distribute shares. It's just transfer shares to other people (addresses).

This may be obvious to everyone, and not worth repeating, but from what I read above, it appears that there’s confusion around the different block chain interfaces in the Peershares protocol.

There are two mechanisms, send shares and distribute dividends.

Send shares is Peercoin’s send coins, just re-labeled. It’s intended for the transfer of peershares between two wallets. Sending shares does not, in any way, interact with the Peercoin network and remains only a record on the Peershares block chain that it was made on.

Distribute dividends, on the other hand, is a cross-network function. An amount of peercoins will be distributed, proportionally to all holders (as of a certain date), based on their peershares holdings on that block chain. No shares are transferred during this action, but transactions are recorded on the Peercoin block chain.

Anyone is able to offer a dividend – though, in practice, it’s most likely going to be the company, organization or individual that originally launched the particular Peershares offering.

The reason that everyone has the “distribute dividends” menu item is that the block chain has no concept of “ownership” when it comes to the offering. It’s plausible that in the future, either through a distributed voting mechanism, or some alternative designation, that the entity processing the dividends won’t be the one that launched the block chain. Therefore, everyone needs the ability to conduct it.

In the future, during a UI overhaul, this function would benefit from being moved to a different section of the application, or nested under some sort of “Offering Tools” area.