Wow, is Devshares ready?

[davidpbrown]

I have a node running but no connections, I assume the network is not live yet.  Anyone know when we will be live?

I've just put 108.61.167.133:2009 back up and it's getting a few connections but really until the devs produce a new genesis block and as per the mumble some tool to take private keys from BTS safely into DVS, then we wait for the real start of DevShares when the drop on BTS will allow most people to register delegates. If you're lucky and can see some DVS, you could go play for a while till then.

[jamesc]

I have a node running but no connections, I assume the network is not live yet.  Anyone know when we will be live?

[clayop]

Halp no connections. Who wants to provide seed nodes?

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

[vikram]

Halp no connections. Who wants to provide seed nodes?

[Rune]

I'm looking forward to doing pump n dumps with devshares! It's gonna be really interesting to see what happens to bitassets.

We need to get a DVS gateway to BTS ASAP. This could be run by the same delegate who also props up the price by buying and burning DVS. I think it would be best to have the DVS delegate set a price target in BTS, so if DVS market cap is below, say, 1/1000 of BTS then he buys and burns the entire 100% dilution. If DVS cap is above the target then the diluted BTS is simply burned. As long as it's done through a gateway on the BTS blockchain, fraud will be impossible.

[Xeldal]

Hmm I can't transfer DVS?

Code: [Select]

devshares (unlocked) >>> wallet_transfer 1 DVS xeldal xeldal
10 assert_exception: Assert Exception
key->has_private_key():
    {}
    th_a  wallet.cpp:1568 get_private_key

    {"addr":"DVSHt5Bx1mZuvtMpVMhP63PH912Cub3qAYtJ"}
    th_a  wallet.cpp:1570 get_private_key

    {"recipient":{"id":125,"name":"xeldal","public_data":null,"owner_key":"DVS8QxQKrwMNXaDZEWDTHe1HMm8j2eT18yADeAV2TnEphvz4UJdZh","active_key_history":[["2014-12-20T16:48:40","DVS7jj3TNFkviB1YFxNPAoyn5ipPmAqC1quDmFMHPWJPydwn5u6CN"]],"registration_date":"2014-12-20T16:48:40","last_update":"2014-12-20T16:48:40","delegate_info":null,"meta_data":null},"amount":{"amount":100000,"asset_id":0},"memo":""}
    th_a  transaction_builder.cpp:203 deposit_asset

    {}
    th_a  common_api_client.cpp:3759 wallet_transfer

    {"command":"wallet_transfer"}
    th_a  cli.cpp:579 execute_command

Update:  duplicate accounts

Code: [Select]

NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       APPROVAL       BLOCK PRODUCTION ENABLED
delegate.xeldal *                  DVS7k8nuqx9W8cP2f3QLEegW7gauWpwoWG1a84UaSsuPtb1QcQsfR           2014-12-20T22:13:50   NO             1              NO
delegate.xeldal                    DVS5D9zmjuteSpv3FeRqR1uxfsj28usL21ZTcc8qovKXVYY49edKx           NO                    NO             1              N/A

Well I managed to screw something up.  I'll see if I can remember what I did.
1) built on 1st machine created accounts xeldal(registered) and delegate.xeldal (not registered)
2) built on 2nd machine imported xeldal , created new account  delegate.xeldal and registered
3) tried to transfer 1 DVS on 2nd machine... produced above error
4) successfully made transfer on 1st machine
5) balance changed on 2nd machine ... still unable to make transfers on 2nd machine

private keys match for xeldal on both machines but only 1 of them can make transactions.

Now I would like to remove/rename one of the duplicates ... not sure how to specify
wallet_account_rename maybe should take public key as identifier as well as the name.

update: I guess you can't rename a registered account so wallet_account_rename changed the unregistered account, which is what I needed. 

[jshow5555]

https://github.com/BitShares/bitshares/blob/6541b0d8b8684392c9a228321476ab27930a4de0/snapshots/build_devshares.py

I believe with v0.4.28-dev1 comes build_devshares.py that is different  from the one in the link above.

[graffenwalder]

Great, devshares already fixing problems.

If this would have happend with play, sparkle, RPC or whatever. It could have been a more serious problem.

[Xeldal]

Actually what are you basing the total supply off of? Is AGS 5 orders of magntiude relatively or to some specific fixed # you expect? I just made the max supply 3*10^something

e5 was just a wild guess based on an expected ~# relative to what I received from importing AGS keys.  I imported a relatively large BTS key and got something like 10 DVS so I figured something was amiss.  Perhaps just my own missunderstanding. IDK

[toast]

https://github.com/BitShares/bitshares/blob/6541b0d8b8684392c9a228321476ab27930a4de0/snapshots/build_devshares.py

[toast]

Actually what are you basing the total supply off of? Is AGS 5 orders of magntiude relatively or to some specific fixed # you expect? I just made the max supply 3*10^something

[toast]

Perhaps user error but I've imported private keys with the qt into a new devshares wallet, expecting to see devshares reflecting BTS balances ~14th Dec.. but nothing appeared.

I was expecting then to throw those DVS at the live devshares client's wallet to avoid issues.

Am I missing something obvious.. do we know the genesis block is correct for that snapshot?.. Any ideas??

I have no problem with a Bitcoin AGS privkey import.
But i get nothing when i try it with a Bitshares privkey.

Same here.   I get something but it is around 5 orders too small DVS

If that's true it sounds like an error on our part. Will look into it sometime. Consider this network bound for a reset until we figure out what's wrong I guess

[Xeldal]

Perhaps user error but I've imported private keys with the qt into a new devshares wallet, expecting to see devshares reflecting BTS balances ~14th Dec.. but nothing appeared.

I was expecting then to throw those DVS at the live devshares client's wallet to avoid issues.

Am I missing something obvious.. do we know the genesis block is correct for that snapshot?.. Any ideas??

I have no problem with a Bitcoin AGS privkey import.
But i get nothing when i try it with a Bitshares privkey.

Same here.   I get something but it is around 5 orders too small DVS

[JA]

Perhaps user error but I've imported private keys with the qt into a new devshares wallet, expecting to see devshares reflecting BTS balances ~14th Dec.. but nothing appeared.

I was expecting then to throw those DVS at the live devshares client's wallet to avoid issues.

Am I missing something obvious.. do we know the genesis block is correct for that snapshot?.. Any ideas??

I have no problem with a Bitcoin AGS privkey import.
But i get nothing when i try it with a Bitshares privkey.

[davidpbrown]

Perhaps user error but I've imported private keys with the qt into a new devshares wallet, expecting to see devshares reflecting BTS balances ~14th Dec.. but nothing appeared.

I was expecting then to throw those DVS at the live devshares client's wallet to avoid issues.

Am I missing something obvious.. do we know the genesis block is correct for that snapshot?.. Any ideas??

[davidpbrown]

I recomend moving all funds after import to a new wallet.

!?.. could a BTS wallet not just accept the DevShares as a new asset and then the users transfer those devshares to an unstable new devshares wallet instead?

[pc]

Awesome!
Will you provide binaries?

Linux packages for CentOS, Fedora + openSUSE: http://software.opensuse.org/download.html?project=home%3Ap_conrad%3Abts&package=DevShares

[clayop]

Waiting for windows/Mac client 

[Harvey]

I noticed that it is quite expensive to register a 100% delegates in the Dev.
The registration fee is around 5 Million Dev. I only managed to register a 2% delegates.
         harvey.lion

haha~   

[fluxer555]

Can we please use the system that the new PTS uses, which does not actually import private keys?

[jshow5555]

I love it: "theft is legitimate" given our goal is to produce trust less systems.  This is the way to go.

Since we claim the shares with real private keys, we should mention that theft of any private key is not allowed.

Or a design so we don't use a real private key....

I recomend moving all funds after import to a new wallet.

Will the vesting balances be movable? If not, how is this suggestion working for them?

[CryptoPrometheus]

I love it: "theft is legitimate" given our goal is to produce trust less systems.  This is the way to go.

Since we claim the shares with real private keys, we should mention that theft of any private key is not allowed.

Or a design so we don't use a real private key....

I recomend moving all funds after import to a new wallet.

How do I do this with AGS?

[bytemaster]

I love it: "theft is legitimate" given our goal is to produce trust less systems.  This is the way to go.

Since we claim the shares with real private keys, we should mention that theft of any private key is not allowed.

Or a design so we don't use a real private key....

I recomend moving all funds after import to a new wallet. 

[jamesc]

I love it: "theft is legitimate" given our goal is to produce trust less systems.  This is the way to go.

Since we claim the shares with real private keys, we should mention that theft of any private key is not allowed.

Or a design so we don't use a real private key....

[Ander]

Given that it will be much, much easier to manipulate the price of DevShares than BTS, we might be able to test the effects of black swan events on bitAssets.  For example, dump a ton of devshares and crash the price by 90% in a minute.  See what happens to the asset markets in devshares!

This would be useful for helping to come up with defenses against BTS suffering these same attacks and manipulations.

[arhag]

Does this mean, we have to wait for an exchange to enlist DevShares before markets can be openend? I guess DevShares will be dependent on price feeds to.

Or will delegates have the oppurtunity to come up with their own prices until then?
This would make DevShares an interesting trading experience

I think that would be really fun actually. If delegates have been elected and are ready to publish price feeds but the exchanges haven't added DVS yet, why not just have all the delegates agree to publish some arbitrary price feed (say 300 DVS/USD which would correspond to a $10,000,000 market cap). Then we could allow short sellers choose any price greater than that (in DVS/USD) to short sell DevUSD. If some people pick a price of DVS (in USD) that is too high (or low in DVS/USD price), then when the true price feeds come in they would end up being margin called and also may not have enough collateral to back the DevUSD debt. This would be a great test of what happens during a black swan event and how the network can recover from it over time . Also, we would see how good the internal DevShares exchange is at price discovery. If things work out well, the starting price on exchanges like BTER and BTC38 should be very close to the price on the DevShares DevUSD/DVS exchange.

By the way, no one has bothered registering any accounts on the blockchain yet? Is the v0.4.28-dev1 release for DevShares ready to be used?

[graffenwalder]

Does this mean, we have to wait for an exchange to enlist DevShares before markets can be openend? I guess DevShares will be dependent on price feeds to.

Or will delegates have the oppurtunity to come up with their own prices until then?
This would make DevShares an interesting trading experience

[Ander]

The blog answered my questions too.  Equal split BTS, PTS, and AGS.

[graffenwalder]

http://bytemaster.github.io/update/2014/12/19/The-Value-of-DevShares.html

I feel this kind of disclaimer is necessary to encourage exchanges to participate in our development network without fear of any liability. Some people will have a hard time managing their expectations, but it will be up to the community to remind them of the social consensus on the DevShares chain that there are no scams, “theft” is legitimate, and trust is a gamble.

loving this bit

[mf-tzo]

Never mind...I just read BM's blog explaining devs shares and answered all my questions 

http://bytemaster.github.io/update/2014/12/19/The-Value-of-DevShares.html

Only thing is how to claim them, what wallet we download and when we can start trading them but I guess the relevant info will follow whenever things are ready...

[pc]

http://bytemaster.github.io/update/2014/12/19/The-Value-of-DevShares.html

[Ander]

It used Dec 14th, same as Sparkle and PTS.

Which chains were share dropped on for this again?
Was it all of BTS, PTS and AGS?

[clayop]

Awesome!
Will you provide binaries?

[mf-tzo]

Sorry to ask that but what exactly is devshares again? If I remember correctly these will be used to test things out.
Do these have a value?
How do we claim them?
How do we trade them?

Thanks

[bytemaster]

Really Nice. Is a snapshot date already announced?

It used Dec 14th, same as Sparkle and PTS.

[graffenwalder]

Really Nice. Is a snapshot date already announced?

[toast]

we're on block 950 =)

[CLains]

They said this week, so yes - WOW! Development is lightning 

[clayop]

https://github.com/BitShares/bitshares/releases/tag/v0.4.28-dev1

I'm not sure whether it is end-user version. But... Wow!