Quote from: GaltReport on July 28, 2014, 12:12:25 am

I didn't know that.  That's cold man.

Think about it... let's say the slate for block production is as follows:

D1, D2, D3, D4, D5. Let's say D1 is a good honest guy and D2-D5 are playing dirty.

D1 produces a block, but as soon as he does, D2 builds a longer chain based on last block before D1 and marks it as missed. Then D3 confirms it, and so does D4 and D5. Now they have the longest chain of decent looking blocks. While good guy D1 has bad rep.

After reading about Liberty Reserve, I don't see much similarity here. Bitshares isn't acting as a depository or a "real" currency exchange. People are going to have to buy BTSX from elsewhere and then use it to trade.

Bank-Coinbase-BTer-BitsharesX
Similarly,
Bank-paypal-Ebay. If someone is laundering money through paypal and then buying things on Ebay, the ebay sellers aren't charged with AML crimes. Neither does Ebay.

I am no lawyer though. It be nice to know for sure.

Quote from: bytemaster on July 27, 2014, 06:48:50 pm

I think the latency metric is very important (only valid if your data collection node stays online the whole time).   A good node will have a median latency of 0.   

Right now I just connect to the client via JSONRPC. Any pointers as to where/how I could get that data from so I can include in analysis? Or do I need to plug into the toolkit source code directly?

Quote

Another metric is "who came before and after me" when I missed a block.  Sometimes it is the node that comes after you that "skips" your block and makes it look like you missed it.   Because of the shuffle it would appear as if everyone is "randomly" missing a block when in reality it is everyone who goes before Attacker always misses a block.

Funny you should mention that, I was just about to start doing an analysis of missed blocks before each delegate! Since as we all know a bad delegate could simulate missed block for someone else, so that they get kicked out. It gets worse - if you have a few delegates, you could target one specific delegate you want out, and collaborate to create bad rep for the good guy. It will be interesting how it unfolds, as the competition heats up. This is why I thought limiting to 100 delegates is tough because it will produce fierce competition and some bad behavior will ultimately come out of it. That said - it's also a good thing because we will analyze and find ways to strengthen the network. This is uncharted territory.

Have you tried wallet_account_rename in the console?

I have run into similar issues.  I reboot regularly to prevent it.  ...

Quote from: CLains on July 27, 2014, 01:15:56 pm

Another idea, "force vote" button that automatically sends all your funds back to yourself.

 



PS and when you press the button a windows message should appear that says something like:

"You have successfully voted for X delegates
delegate 1, delegate2 ....,... etc.

Thank you for making the network more secure !!!
You can change your votes whenever you want or vote for additionall
delegates up to 101. If you would find helpfull some recommendations for the most trusted delegates be comfortable to check some popular slate id's
that will give you some extra BTSX bonus(?)..." 

Quote from: GaltReport on July 26, 2014, 06:34:25 pm

Quote from: jcalfee1 on July 26, 2014, 05:29:40 pm

'freeworm' looked up a withdraw for me giving me a transaction id.   I don't see this in my account, nor do I see my "Account Key" in the transaction.  Is there anyway to figure out what the registered account name is from this transaction?

>> blockchain_get_transaction 651b36f9

I believe transaction ID he is referring to is on Bter in your withdraw history for BTSX.

I have a local account name conflicting with a registered account name.  I'm trying to figure out how to rename the unregistered/local account to resolve this.  I'm sure the withdraw worked fine.   -thank you

Quote from: GaltReport on July 26, 2014, 02:20:34 am

Ever since upgrading to 0.2.3 everything works worse for me.  Wallet has issues registering accounts, transferring to myself and my delegate has started dropping blocks. 

I noticed a spike in my delegate cpu sometime after midnight last night, was also near the time my bter transfer of yesterday went through, which also killed my ability to transfer today.

Something seems odd to me....

Quote from: GaltReport on July 26, 2014, 02:35:13 am

It must be me then!

I didn't uninstall the old windows wallet when I upgraded, wondering if I should have done that?

I have multiple unregistered accounts that I can't register.  I get an error saying, "Unknown account".

Quote from: GaltReport on July 26, 2014, 05:09:43 am

Might have found the problem.  I see that the accounts I get errors on registering both end in .com

It let me create local accounts that end in .com but I think it can't register them.  Can someone confirm that?  Seems like a bug if it let's you create them with a .com but not register them.

It is not recommended to run delegate nodes using the GUI. It is untested and unsupported.

In addition, any wallet with block production enabled will by default not scan transactions, so you will not see any deposits you may receive.

Account names use the dot to signify child accounts. E.g. to register 'galt.com' you must also control the private key for 'com'.