Main Menu

Dry Run 2: The Real Deal

Started by toast, June 12, 2014, 11:24:02 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages 1 2 3 4 5 6 7 8 9 10 11 12 13 ... 42
User actions

networker

#548
June 18, 2014, 02:17:56 PM
Quote from: spartako on June 18, 2014, 11:07:37 AM
Quote from: alexxy on June 18, 2014, 09:58:27 AM
Can someone vote for my delegate?

I just voted for you ;)

Can you vote me for the delegate?
I have been testing for ten days, just solve the forking problem and need to test block produce.
Thank you in advance
my account is networker.  You sent me XTS before.

HackFisher

#547
June 18, 2014, 02:00:16 PM
Quote from: vlight on June 18, 2014, 12:27:45 PM
I missed the  entire dry run 2, because it became impossible to install on a server with only 1GB RAM.

2GB seems enough. It's more expensive though.

I'm running a VPS with 1GB, you might need this to compile toolkit with only 1GB RAM:

https://www.digitalocean.com/community/tutorials/how-to-add-swap-on-ubuntu-14-04
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

xeroc

#546
June 18, 2014, 01:58:23 PM
Quote from: xeroc on June 18, 2014, 06:54:13 AM
They missed to tell us about a recent commit:
https://github.com/BitShares/bitshares_toolkit/commit/55053c244f3057841b86a5b46fad654d7e1ce636

You need to run:
wallet_toggle_delegate_block_production <delegate> true

In order for delegates to produce blocks!

EDIT: doesn't seem to work .. i reverted to the previous commit to keep my delegate online AND producing blocks
Bytemaster fixed an issue with that feature:

It's now called
wallet_enable_delegate_block_production <delegate> true

bytemaster

#545
June 18, 2014, 01:29:51 PM
Quote from: emski on June 18, 2014, 01:25:51 PM
Quote from: Xeldal on June 18, 2014, 01:21:37 PM
Im wondering, if we're manually adding a bunch of delegates for Dry Run 3.  Would it not be just as easy, for the people with existing init-delegates, to change the name of one of them to something more desirable?  rather than making an additional one.
Good point!
I like it.

I get toast on it.
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

emski

#544
June 18, 2014, 01:25:51 PM
Quote from: Xeldal on June 18, 2014, 01:21:37 PM
Im wondering, if we're manually adding a bunch of delegates for Dry Run 3.  Would it not be just as easy, for the people with existing init-delegates, to change the name of one of them to something more desirable?  rather than making an additional one.
Good point!
I like it.
[url="https://bitsharestalk.org/index.php/topic,9857.0.html"]https://bitsharestalk.org/index.php/topic,9857.0.html[/url]

Xeldal

#543
June 18, 2014, 01:21:37 PM
Im wondering, if we're manually adding a bunch of delegates for Dry Run 3.  Would it not be just as easy, for the people with existing init-delegates, to change the name of one of them to something more desirable?  rather than making an additional one.

bytemaster

#542
June 18, 2014, 01:11:00 PM
Quote from: vlight on June 18, 2014, 12:27:45 PM
I missed the  entire dry run 2, because it became impossible to install on a server with only 1GB RAM.

2GB seems enough. It's more expensive though.

This is a g++ limitation as our code does not require that much to run.   
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

bytemaster

#541
June 18, 2014, 01:10:08 PM
Quote from: mauritso on June 18, 2014, 08:43:09 AM
Quote from: bnoble1206 on June 17, 2014, 04:50:01 PM

Is there any way we could get the wiki updated with the recently added debug commands? Like list_errors and max_connections and all that? That way those of us who came a little late can be more helpful.


Sent from my iPhone using Tapatalk

https://github.com/BitShares/bitshares_toolkit/wiki should be done. Generated with the api json documents.

Created a pull request: https://github.com/BitShares/bitshares_toolkit/pull/332
Manually fixed the JSON.

Thanks
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Kenof

#540
June 18, 2014, 01:02:06 PM Last Edit: June 18, 2014, 01:06:08 PM by Kenof
It worked for me on dry run 1 with 1GB RAM, but on dry run 2 server just crashed when installing. After setting instance with 2GB RAM it now works like charm. OS is Ubuntu 14.04.

Hope to get elected to be active delegate in the next dry run. It could take very large marketing campaign in the future to stay a delegate.
Making life easier.

svk

#539
June 18, 2014, 12:31:11 PM
Quote from: vlight on June 18, 2014, 12:27:45 PM
I missed the  entire dry run 2, because it became impossible to install on a server with only 1GB RAM.

2GB seems enough. It's more expensive though.

I've got it up and running on a 512mb Amazon free tier micro server so that's not quite true. First compile failed, then I setup a 1gb swap and it worked.

It takes forever to compile though so by the time it's done, lots of new changes have alreade been pushed, lol.
Worker: dev.bitsharesblocks

spartako

#538
June 18, 2014, 11:07:37 AM
Quote from: alexxy on June 18, 2014, 09:58:27 AM
Can someone vote for my delegate?

I just voted for you ;)
wallet_account_set_approval spartako

alexxy

#537
June 18, 2014, 09:58:27 AM
Can someone vote for my delegate?
Vote for my delegates! alexxy | lexx
PTS: PmraxfZ852y9oEKrYMLX1ee3e4qRWPUTFC
BTS: alexxy

mauritso

#536
June 18, 2014, 08:43:09 AM
Quote from: bnoble1206 on June 17, 2014, 04:50:01 PM

Is there any way we could get the wiki updated with the recently added debug commands? Like list_errors and max_connections and all that? That way those of us who came a little late can be more helpful.


Sent from my iPhone using Tapatalk

https://github.com/BitShares/bitshares_toolkit/wiki should be done. Generated with the api json documents.

Created a pull request: https://github.com/BitShares/bitshares_toolkit/pull/332
Manually fixed the JSON.
BTS: maurits

xeroc

#535
June 18, 2014, 08:38:00 AM
Quote from: bitcoinerS on June 18, 2014, 08:10:49 AM
Having troubles issuing assets.

Code Select
Usage:
wallet_asset_issue <amount> <symbol> <to_account_name> <memo_message>

Code Select
>>> wallet_asset_issue 1000000 BEE default "Bees are people too"
10 assert_exception: Assert Exception
my->_blockchain->is_valid_symbol( symbol ):
    {}
    th_a  wallet.cpp:1772 issue_asset

Is your account-name really 'default' .. not wallet name... it's accountname .. list your account names via wallet_list_receive_accounts

bitcoinerS

#534
June 18, 2014, 08:10:49 AM
Having troubles issuing assets.

Code Select
Usage:
wallet_asset_issue <amount> <symbol> <to_account_name> <memo_message>

Code Select
>>> wallet_asset_issue 1000000 BEE default "Bees are people too"
10 assert_exception: Assert Exception
my->_blockchain->is_valid_symbol( symbol ):
    {}
    th_a  wallet.cpp:1772 issue_asset
>>> approve bitcoiners
Print
Go Up Pages 1 2 3 4 5 6 7 8 9 10 11 12 13 ... 42
User actions