Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - bdnoble

Pages: 1 2 3 4 5 6 [7] 8
91
General Discussion / Re: Dry Run 5: The Final Countdown
« on: June 24, 2014, 11:45:23 am »
Hey so... How do I increase my max connections? I can't seem to find that command.


Sent from my iPhone using Tapatalk

92
General Discussion / Re: Dry Run 3: A Game of Delegates
« on: June 20, 2014, 11:54:33 am »

I wake up early morning for the test, I registered spartako but my transactions was pending for long time and I believed I was in a fork....so then I have done a BIG mistake and removed all my BitSharesXTS directory without saving my private key :( (I was actually sleeping...)
Then I realized that I was in the good chain and now spartako is lost....I registered a new account spartako-delegate and voted against spartako.

So please vote AGAINST spartako and vote FOR spartako-delegate.
Free LOVE for everyone vote for spartako-delegate ;)

Add me to the list of people who deleted a wallet and lost the keys. :P bdnoble-1 is no good but I think bdnoble is working. :)

Good thing this is a test run. I think we were all a little too excited.


Sent from my iPhone using Tapatalk

93
General Discussion / Re: Novice question on Windows
« on: June 19, 2014, 06:54:03 pm »

So I was trying to follow the Windows instructions here: https://github.com/nmushegian/bitshares_toolkit/blob/master/BUILD_WIN32.md

I created a directory and downloaded CMake, Boost, BerkeleyDB, toolkit and OpenSSl to it.

I tried to set the enviroment run setenv.bat and I get this error
Code: [Select]
C:\BitShares>cd bitshares_toolkit-master

C:\BitShares\bitshares_toolkit-master>setenv.bat
Using C:\BitShares\bitshares_toolkit-master\..\ as Bitshare root directory
The system cannot find the path specified.
The system cannot find the path specified.
Setting up VS2013 environment...
ERROR: Cannot determine the location of the VS Common Tools folder.
Press any key to continue . . .
Sorry, i am a complete Noob. I am trying though

What is the VS common Tools folder? I have the Visual Studio Express edition.

Those instructions for windows are not very well documented. There are many updates to scripts that need to happen in order to make it to work right.

As a novice, I would actually recommend installing a dual boot of ubuntu because most of the developers are running in Linux and the installation is much much easier. And you'll be more likely to have people be able to help you when you have problems.

I started trying to install on windows but gave up and switched to ubuntu after many hours of problems while installing.


Sent from my iPhone using Tapatalk

94
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 19, 2014, 05:28:14 pm »

Ok i figured it out.  2 things.

1 you need to wallet_account_create before you import, it won't automatically create the account
2 wallet_account_create doesn't like uppercase  :-\

I got it to import provided these 2 things.

I feel like this process should be documented better. I went through the exact same process and it took me a while before I was able to get my PTS imported as well.


Sent from my iPhone using Tapatalk

95
General Discussion / Re: Bitshares X
« on: June 19, 2014, 03:41:30 pm »
When I import my PTS wallet into XT currently it seems to be about 3 XTS per PTS. Not sure if that is going be the case for X though.


Sent from my iPhone using Tapatalk

96
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 19, 2014, 03:37:04 pm »

How to import PTS wallet?

I see the bitcoin, electrum, multibit, armory, and keyhotee import commands. 

Is there no command for PTS yet?

You can either import the private key directly or you can import the PTS wallet.dat using the bitcoin import.


Sent from my iPhone using Tapatalk

97
General Discussion / Re: Names for dry run 3
« on: June 18, 2014, 04:19:19 pm »
by popular request we are letting you have names for initial delegates for dry run 3.

Please give your name and key here.

But seriously it makes no difference, for the real thing we will call everyone "untrusted-delegate-do-not-vote-XX".

Unless I'm missing something, all the delegates currently waiting in line don't have nearly enough shares to make any difference in the votes.... so many of the init-delegates have millions of vote points. How can any of them be voted out?

Seems like the only way is to market to some huge investors who have lots of shares. And how do we do that? The only ones I know of are 3I. And that is especially true for this dry run right? So who has all the fat stacks of XTS that wants to vote for me?!?  :D

bdnoble-1       XTS82f63YBpbTRWz549eQbV3kReyyvxFdDH8hhCgYkACxv1qTNgaA

98
General Discussion / Re: Names for dry run 3
« on: June 18, 2014, 03:53:07 pm »
bdnoble-1       XTS82f63YBpbTRWz549eQbV3kReyyvxFdDH8hhCgYkACxv1qTNgaA

99
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 17, 2014, 04:50:01 pm »

We will be launching a new Dry Run 3 chain and it will have the following changes:

1) all active delegates that produced 0 blocks will be removed
2) everyone that registered as a delegate will take their place prioritized by vote.
3) we have fixed the wallet_withdraw_delegate_pay operation which would introduce a hard fork
4) we will increase the block interval to 30 seconds
5) we will be updating the on-the-wire protocol to communicate extra information such as:
      a) latency between nodes
      b) additional information about node connectivity.
      c) persistent node IDs derived from a public key

With these network updates we should be able to map out the full network of connected nodes (nothing the NSA cannot do anyway).  Using this information delegates can optimize their network connections and users can verify geographic diversity.   

The new test net will launch once we finalize the on-the-wire protocol updates so probably tonight or tomorrow. 

A new GUI wallet is also close to release.

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

100
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 17, 2014, 03:37:35 pm »

So I finally was able to import my PTS wallet.dat. Apparently I just had to wait long enough for the blockchain to sync. And now I am registered as a delegate on the waiting list! Anyone want to vote for me?! :D "bdnoble-1" I can send some votes back too. We gotta replace some more of these init-delegates. :)
You got trust from me ..
+ You should give yourself some trust and move your XTS from your wallet back to your own wallet so that your vote is broadcasted!

Hi I trusted everyone here, moving XTS around but the problem is:
+ When I vote for someone else my votes decreased.
+ When I vote back myself (transfer XTS back) I believe their votes go down

So we are back to square 1.

Bytemaster any way to get all the delegates in the queue (named) as delegates. I would like and (everyone else I guess) to test my VPS.

The challenge we have is that our 'test stake' isn't enough to fully elect all the delegates (meaning things are working).  I used my stake to vote out some of the non-performing initial delegate keys in an attempt to make room for everyone else.

So are we going to have to vote down all the init delegates again when the official release hits? Or is there going to be some kind of snapshot from this test net? Would it be more effective to vote down init delegates than to vote up everyone else?


Sent from my iPhone using Tapatalk

101
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 17, 2014, 01:46:56 pm »

So I finally was able to import my PTS wallet.dat. Apparently I just had to wait long enough for the blockchain to sync. And now I am registered as a delegate on the waiting list! Anyone want to vote for me?! :D "bdnoble-1" I can send some votes back too. We gotta replace some more of these init-delegates. :)
You got trust from me ..
+ You should give yourself some trust and move your XTS from your wallet back to your own wallet so that your vote is broadcasted!

Right, of course! I'll go do that on my lunch break. :)


Sent from my iPhone using Tapatalk

102
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 17, 2014, 01:42:35 pm »
So I finally was able to import my PTS wallet.dat. Apparently I just had to wait long enough for the blockchain to sync. And now I am registered as a delegate on the waiting list! Anyone want to vote for me?! :D "bdnoble-1" I can send some votes back too. We gotta replace some more of these init-delegates. :)


Sent from my iPhone using Tapatalk

103
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 16, 2014, 05:02:52 pm »


I know I am a little late to the party, but I built the latest with a clean .BitsharesXTS dir and tried to import my wallet.dat from PTS using wallet_import_bitcoin and it seemed like it worked but I don't have any XTS. Am I doing something wrong? Could I get some XTS to try to register as a delegate with? :)

Code: [Select]
importing PrWXTV7BMNJikS36HTJZzdUXKDc4QKjRbz
importing Pkw41LBvT8BEhwiW7osiKtf5yHRah7w8n7
importing 1KakKQR3bGMexAEEuxeiqcEU4yBEd1QAxo
importing 1E1GsFVnh2EAufuekKDsAsR2j2zkrATCrj
OK
bdnoble (unlocked) >>> wallet_rescan_blockchain
Rescanning blockchain...
|----------------------------------------------------------------------------------------------------|
|====================================================================================================|
Scan complete.
OK
bdnoble (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            TRUST LEVEL
bdnoble                            XTS5UJbjAws1os3J8eX2H2HEp3iTs5a2CsqJwb2w23cZvxqjd6vjZ           NO                    0
bdnoble (unlocked) >>> wallet_get_info
{
  "data_directory": "/home/ben/.BitSharesXTS/wallets",
  "last_unlocked_scanned_block_number": 3829,
  "last_locked_scanned_block_number": null,
  "next_child_key_index": 2,
  "default_transaction_priority_fee": {
    "amount": 10000,
    "asset_id": 0
  },
  "state": "open",
  "locked": false,
  "file": "/home/ben/.BitSharesXTS/wallets/bdnoble",
  "scheduled_lock_time": "20140628T024833"
}


I imported mine using private keys.

Have you done wallet_account_balance <- to get the balance
or wallet_rescan_blockchain <- to "refresh"

I did a rescan.

I actually couldn't figure out how to find my private keys from PTS. I did a dumpprivkey on my PTS qt wallet but it said it couldn't find my private key for my address or something like that. So that's why I tried to import the wallet.dat. Has anyone else tried that yet? Is it supposed to be working?


Sent from my iPhone using Tapatalk

Any word on this? Is there some special way to import from PTS wallet.dat that I haven't tried? Could anyone send me some XTS to play with until I figure this out?

XTS5UJbjAws1os3J8eX2H2HEp3iTs5a2CsqJwb2w23cZvxqjd6vjZ


Sent from my iPhone using Tapatalk

104
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 16, 2014, 01:30:38 pm »

I know I am a little late to the party, but I built the latest with a clean .BitsharesXTS dir and tried to import my wallet.dat from PTS using wallet_import_bitcoin and it seemed like it worked but I don't have any XTS. Am I doing something wrong? Could I get some XTS to try to register as a delegate with? :)

Code: [Select]
importing PrWXTV7BMNJikS36HTJZzdUXKDc4QKjRbz
importing Pkw41LBvT8BEhwiW7osiKtf5yHRah7w8n7
importing 1KakKQR3bGMexAEEuxeiqcEU4yBEd1QAxo
importing 1E1GsFVnh2EAufuekKDsAsR2j2zkrATCrj
OK
bdnoble (unlocked) >>> wallet_rescan_blockchain
Rescanning blockchain...
|----------------------------------------------------------------------------------------------------|
|====================================================================================================|
Scan complete.
OK
bdnoble (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            TRUST LEVEL
bdnoble                            XTS5UJbjAws1os3J8eX2H2HEp3iTs5a2CsqJwb2w23cZvxqjd6vjZ           NO                    0
bdnoble (unlocked) >>> wallet_get_info
{
  "data_directory": "/home/ben/.BitSharesXTS/wallets",
  "last_unlocked_scanned_block_number": 3829,
  "last_locked_scanned_block_number": null,
  "next_child_key_index": 2,
  "default_transaction_priority_fee": {
    "amount": 10000,
    "asset_id": 0
  },
  "state": "open",
  "locked": false,
  "file": "/home/ben/.BitSharesXTS/wallets/bdnoble",
  "scheduled_lock_time": "20140628T024833"
}


I imported mine using private keys.

Have you done wallet_account_balance <- to get the balance
or wallet_rescan_blockchain <- to "refresh"

I did a rescan.

I actually couldn't figure out how to find my private keys from PTS. I did a dumpprivkey on my PTS qt wallet but it said it couldn't find my private key for my address or something like that. So that's why I tried to import the wallet.dat. Has anyone else tried that yet? Is it supposed to be working?


Sent from my iPhone using Tapatalk

105
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 16, 2014, 01:13:17 pm »
I know I am a little late to the party, but I built the latest with a clean .BitsharesXTS dir and tried to import my wallet.dat from PTS using wallet_import_bitcoin and it seemed like it worked but I don't have any XTS. Am I doing something wrong? Could I get some XTS to try to register as a delegate with? :)

Code: [Select]
importing PrWXTV7BMNJikS36HTJZzdUXKDc4QKjRbz
importing Pkw41LBvT8BEhwiW7osiKtf5yHRah7w8n7
importing 1KakKQR3bGMexAEEuxeiqcEU4yBEd1QAxo
importing 1E1GsFVnh2EAufuekKDsAsR2j2zkrATCrj
OK
bdnoble (unlocked) >>> wallet_rescan_blockchain
Rescanning blockchain...
|----------------------------------------------------------------------------------------------------|
|====================================================================================================|
Scan complete.
OK
bdnoble (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            TRUST LEVEL
bdnoble                            XTS5UJbjAws1os3J8eX2H2HEp3iTs5a2CsqJwb2w23cZvxqjd6vjZ           NO                    0
bdnoble (unlocked) >>> wallet_get_info
{
  "data_directory": "/home/ben/.BitSharesXTS/wallets",
  "last_unlocked_scanned_block_number": 3829,
  "last_locked_scanned_block_number": null,
  "next_child_key_index": 2,
  "default_transaction_priority_fee": {
    "amount": 10000,
    "asset_id": 0
  },
  "state": "open",
  "locked": false,
  "file": "/home/ben/.BitSharesXTS/wallets/bdnoble",
  "scheduled_lock_time": "20140628T024833"
}


Pages: 1 2 3 4 5 6 [7] 8