[XMS] Moonstone DAC - page 24. | Bitcointalksearch.org

Penetrator10

sr. member

Activity: 405

Merit: 500

Quote from: MisO69 on December 11, 2016, 11:41:51 AM

Quote from: Penetrator10 on December 11, 2016, 11:32:38 AM

Quote from: MisO69 on December 11, 2016, 11:26:54 AM

Quote from: Penetrator10 on December 11, 2016, 11:20:26 AM

Quote from: MisO69 on December 11, 2016, 11:08:37 AM

-snip-

Quote from dev
Remember you have to edit in your config.ini
your witness id with the "" (dont forget to remove the # sign infront of the witness id)
and your private key using your signing key and the corresponding private key which you get from dump_private_keys

I think this is where I made the mistake, I used the signing key from the witness, private key from miso69. I didn't use the public key from the dump_private_keys command. I will fix that and run the node again.

You have to set the signing_key and it's private key in the config.ini file
The 4 lines when you typed dump_private_keys:
the first pair was when you generated your brain key
the second one was when you created your witness

okay so when I do a dump_private_keys I only see one key pair, its the same keypair I got when I did the suggest brain_key_command. pub key, wif priv key. I don't see a keypair associated with the signing key of the witness. Which is the XMS7... key above.

Then you make something wrong in early steps.
https://github.com/moonstonedac/moonstone/wiki/How-to-import-your-key
https://github.com/moonstonedac/moonstone/wiki/How-to-become-a-witness

MisO69

legendary

Activity: 1946

Merit: 1005

My mule don't like people laughing

Quote from: Penetrator10 on December 11, 2016, 11:32:38 AM

Quote from: MisO69 on December 11, 2016, 11:26:54 AM

Quote from: Penetrator10 on December 11, 2016, 11:20:26 AM

Quote from: MisO69 on December 11, 2016, 11:08:37 AM

-snip-

Quote from dev
Remember you have to edit in your config.ini
your witness id with the "" (dont forget to remove the # sign infront of the witness id)
and your private key using your signing key and the corresponding private key which you get from dump_private_keys

I think this is where I made the mistake, I used the signing key from the witness, private key from miso69. I didn't use the public key from the dump_private_keys command. I will fix that and run the node again.

You have to set the signing_key and it's private key in the config.ini file
The 4 lines when you typed dump_private_keys:
the first pair was when you generated your brain key
the second one was when you created your witness

okay so when I do a dump_private_keys I only see one key pair, its the same keypair I got when I did the suggest brain_key_command. pub key, wif priv key. I don't see a keypair associated with the signing key of the witness. Which is the XMS7... key above.

MisO69

legendary

Activity: 1946

Merit: 1005

My mule don't like people laughing

Okay now I'm getting this..

Code:

2001211ms th_a       application.cpp:505           handle_block         ] Got block: #90042 time: 2016-12-11T16:33:21 latency: 207 ms from: georgeandrews  irreversible: 90025 (-17)
2004211ms th_a       application.cpp:505           handle_block         ] Got block: #90043 time: 2016-12-11T16:33:24 latency: 207 ms from: morden  irreversible: 90028 (-15)
2007004ms th_a       witness.cpp:200               block_production_loo ] Not producing block because I don't have the private key for XMS76G3JYrfxTfYWdiA3nxvJ9taJmUkuXeLZPYq5exCknD2acPwSw
2008004ms th_a       witness.cpp:200               block_production_loo ] Not producing block because I don't have the private key for XMS76G3JYrfxTfYWdiA3nxvJ9taJmUkuXeLZPYq5exCknD2acPwSw
2009004ms th_a       witness.cpp:200               block_production_loo ] Not producing block because I don't have the private key for XMS76G3JYrfxTfYWdiA3nxvJ9taJmUkuXeLZPYq5exCknD2acPwSw
2010148ms th_a       application.cpp:505           handle_block         ] Got block: #90044 time: 2016-12-11T16:33:30 latency: 143 ms from: biodragon  irreversible: 90029 (-15)
2013207ms th_a       application.cpp:505           handle_block         ] Got block: #90045 time: 2016-12-11T16:33:33 latency: 203 ms from: riverhead  irreversible: 90030 (-15)

That key is the signing_key when you do the get_witness miso69 command.

Was it right the first time or is this something that I have to wait for a maintenance period to correct?

Penetrator10

sr. member

Activity: 405

Merit: 500

MisO69

legendary

Activity: 1946

Merit: 1005

My mule don't like people laughing

Penetrator10

sr. member

Activity: 405

Merit: 500

cupscrypto

newbie

Activity: 23

Merit: 0

Bitshares clone, must be the first !!

MisO69

legendary

Activity: 1946

Merit: 1005

My mule don't like people laughing

My node isn't producing blocks and everything I have tried doesn't seem to correct the problem. I even tried to run this on an allstream VPS.

This is the error I get producing blocks..

Code:

393220ms th_a       application.cpp:505           handle_block         ] Got block: #89536 time: 2016-12-11T16:06:33 latency: 236 ms from: penetrator10  irreversible: 89516 (-20)
396153ms th_a       application.cpp:505           handle_block         ] Got block: #89537 time: 2016-12-11T16:06:36 latency: 169 ms from: riverhead  irreversible: 89519 (-18)
399102ms th_a       application.cpp:505           handle_block         ] Got block: #89538 time: 2016-12-11T16:06:39 latency: 117 ms from: kunfu  irreversible: 89521 (-17)
401985ms th_a       witness.cpp:181               block_production_loo ] Got exception while generating block:
10 assert_exception: Assert Exception
witness_obj.signing_key == block_signing_private_key.get_public_key():
    {}
    th_a  db_block.cpp:327 _generate_block

    {"witness_id":"1.6.26"}
    th_a  db_block.cpp:411 _generate_block

    {}
    th_a  db_block.cpp:309 generate_block
401985ms th_a       witness.cpp:212               block_production_loo ] exception prodcing block
402984ms th_a       witness.cpp:206               block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
403984ms th_a       witness.cpp:206               block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
405157ms th_a       application.cpp:505           handle_block         ] Got block: #89539 time: 2016-12-11T16:06:45 latency: 172 ms from: biodragon  irreversible: 89524 (-15)
408154ms th_a       application.cpp:505           handle_block         ] Got block: #89540 time: 2016-12-11T16:06:48 latency: 169 ms from: morden  irreversible: 89525 (-15)

Any Ideas?

Penetrator10

sr. member

Activity: 405

Merit: 500

vvinam voted for you too

bitass

member

Activity: 83

Merit: 10

Is this trading on exchange?

BitSharesToDaMoon

newbie

Activity: 9

Merit: 0

I have a question too:

On which area is your dac going to be better than bitshares ?

logictense

hero member

Activity: 2147

Merit: 518

Id love to have a clarification on two things:

1) Does moonstone utilize Bitshares source code? Is it possible that a proprietary technology similar to Graphene is to be developed on top of the platform, aimed to resemble a highly compact decentralized bundle, free of malignant bias on the part of chinese manipulators. The latter seems to be the case of negativity and ill temper surrounding Bitshares. Id rather invest in an alternative asset built from the ground up with the liberty in mind, than get back to a bunch of cocky gatekeepers.

2) Are there any plans to develop moonstone DEX?

vvinam

full member

Activity: 202

Merit: 100

Quote

vote_for_witness vvinam penetrator10 true true
{
"ref_block_num": 19924,
"ref_block_prefix": 1690413156,
"expiration": "2016-12-11T12:32:15",
"operations": [[
6,{
"fee": {
"amount": 20060,
"asset_id": "1.3.0"
},
"account": "1.2.33",
"new_options": {
"memo_key": "XMS6jdd7zNdNuLko2N2ZkkFZN45LCKMWAgqkz6XMb425tr4CGLa1N",
"voting_account": "1.2.5",
"num_witness": 0,
"num_committee": 0,
"votes": [
"1:31",
"1:34"
],
"extensions": []
},
"extensions": {}
}
]
],
"extensions": [],
"signatures": [
"2045d261f3b9422d4e950764503c2deab311ba6e58d02e66acef200c98375d8f5f3c913dde6fc63 afd63e7083e1e3136067c0cb72d6b8f17987feb75fd876c0dd5"
]
}

voted for penetrator10

vvinam

full member

Activity: 202

Merit: 100

Quote

vote_for_witness vvinam miso69 true true
{
"ref_block_num": 19886,
"ref_block_prefix": 1368080331,
"expiration": "2016-12-11T12:30:15",
"operations": [[
6,{
"fee": {
"amount": 20060,
"asset_id": "1.3.0"
},
"account": "1.2.33",
"new_options": {
"memo_key": "XMS6jdd7zNdNuLko2N2ZkkFZN45LCKMWAgqkz6XMb425tr4CGLa1N",
"voting_account": "1.2.5",
"num_witness": 0,
"num_committee": 0,
"votes": [
"1:31",
"1:37"
],
"extensions": []
},
"extensions": {}
}
]
],
"extensions": [],
"signatures": [
"20078d38727b4b4d7b316a2e24c6a226a5fdc40cfce1da04591a04f19b4e6181f5751991448c973 9d569d699d38fe139264eab4b8582ae89ff2d73519802da7e75"
]
}

Voted for miso69

vvinam

full member

Activity: 202

Merit: 100

Quote from: Korvin on December 10, 2016, 07:57:53 PM

Could someone vote for my witness ("korvin").. pretty please

I am sitting in the witness queue, and just watching others forging blocks.. Sad

Will surely vote in reply! Cool

Quote

vote_for_witness vvinam korvin true true
{
"ref_block_num": 19851,
"ref_block_prefix": 609887538,
"expiration": "2016-12-11T12:28:24",
"operations": [[
6,{
"fee": {
"amount": 20060,
"asset_id": "1.3.0"
},
"account": "1.2.33",
"new_options": {
"memo_key": "XMS6jdd7zNdNuLko2N2ZkkFZN45LCKMWAgqkz6XMb425tr4CGLa1N",
"voting_account": "1.2.5",
"num_witness": 0,
"num_committee": 0,
"votes": [
"1:31",
"1:47"
],
"extensions": []
},
"extensions": {}
}
]
],
"extensions": [],
"signatures": [
"1f57fdc49e8903ecc500f20428d17cb67dcf11aaf148fe54c0e8e0a338d224e4b954aeab391a25f 91d8b97fe19d625d963b48d763c5af245814643410cef3db5de"
]
}

for korvin :d

theboccet

legendary

Activity: 1064

Merit: 1000

thank you so much vinnam!!!!
looking for new developments like skar showed Wink

vvinam

full member

Activity: 202

Merit: 100

Quote

unlocked >>> vote_for_witness vvinam theboccet true true
vote_for_witness vvinam theboccet true true
{
  "ref_block_num": 16537,
  "ref_block_prefix": 1623303812,
  "expiration": "2016-12-11T09:33:15",
  "operations": [[
   6,{
   "fee": {
   "amount": 20056,
   "asset_id": "1.3.0"
   },
   "account": "1.2.33",
   "new_options": {
   "memo_key": "XMS6jdd7zNdNuLko2N2ZkkFZN45LCKMWAgqkz6XMb425tr4CGLa1N",
   "voting_account": "1.2.5",
   "num_witness": 0,
   "num_committee": 0,
   "votes": [
   "1:31"
   ],
   "extensions": []
   },
   "extensions": {}
   }
   ]
  ],
  "extensions": [],
  "signatures": [
   "1f0c8791cd90e087b1317f45a03eefca2b3471216de9a8dfedba19b45d2205bbf21fae8aa4f7d1c 232a1b01f85dbd763dfdb76fccd47f42a7f394d07050cfeae99"
  ]
}

vote for theboccet Cheesy

moonstonedac

full member

Activity: 196

Merit: 100

To maintain fairness, I will not accept requests from brand new bitcointalk accounts.

moonstonedac

full member

Activity: 196

Merit: 100

Quote from: drays on December 10, 2016, 06:27:38 PM

Interesting project

I've installed a node (steps 1-3), I am waiting for the dev to reply to my PM

Meanwhile I have a question - is there an easy way to see all commands wallet can run? Of course, here (https://github.com/moonstonedac/moonstone/blob/f131528ad2ad45b765750ba05ef45c627f4e5478/libraries/wallet/include/moonstone/wallet/wallet.hpp) I can find some info, but a nice short command like "help" could be helpful

you can use this for now
http://docs.bitshares.eu/api/wallet-api.html

Korvin

newbie

Activity: 44

Merit: 0

Quote from: theboccet on December 10, 2016, 08:14:39 PM

Voted for you korvin!!! not for a vote reply but just because everyone deserve mining it for future profit or learning Wink

Much appreciated! Lets run this baby, its fun

If in addition to fun it brings some profit in future, it'll be a nice bonus

Topic: [XMS] Moonstone DAC - page 24. (Read 33894 times)