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.


Topics - toast

Pages: 1 ... 5 6 7 8 9 10 11 [12] 13 14 15 16 17 18 19
166
General Discussion / XT GUI - v0.0.3 - OS X and Windows
« on: June 20, 2014, 11:27:22 pm »
Locking this thread because v0.0.3 will not be compatible with dry run 5.




OS X:  http://bitshares.org/BitSharesXT-0.0.3.dmg
Windows:  http://bitshares.org/documentation/BitSharesXT.exe   <--- quite buggy, don't file issues yet

Edit: If you crash on load, try deleting any existing data directories.
  If you jump straight into the wallet without going into login screen, right click and click "reload".

File bugs here:  https://github.com/BitShares/web_wallet/issues
UI suggestions are not bugs - wait until Cass does a restyle before telling us it is ugly

167
General Discussion / Dry Run 4: A New Hope
« on: June 20, 2014, 08:46:34 pm »
Quote
Hey everyone I am sad to report that we have to reset this dry run due to a major flaw in the initial condition setup resulting in the negative votes-for everyone saw.  Unfortunately I cannot fix this without a reset.

New chain has launched that fixes this issue and the double registration issue.

Let's begin!

* Step 1 **REQUIRED**: Open this in another tab   https://www.youtube.com/watch?v=_D0ZQPqeJkk

* Step 2: Wipe all your old data-dirs. Note that you might have both  ~/.BitSharesXTS  and  ~/BitShares\ XTS  - kill them all.

* Step 3: Pull latest and build.

* Optional Step 4:  If you are an initial delegate and a good citizen, do what you did before (import old private keys, make sure to wallet_enable_delegate_block_production). Details are sparse on purpose, since you probably want to skip this and go straight to 5.

* Step 5: Follow this guide: https://github.com/BitShares/bitshares_toolkit/wiki/DPOS-Registering-Names-And-Delegates

You will notice that you need funds to register your name / register as delegate. You have two options:
* import a key with funds
* ask someone nicely

This is the tech support thread. We'll open another related to delegate campaigns in the next day or two.

Edit: Blocks will be reaaaal slow near the start. Initial delegates, get online!

168
General Discussion / Dry Run 3: A Game of Delegates
« on: June 20, 2014, 12:26:19 am »
In this dry run, all initial delegates start with tons of downvotes. This means any new delegate is automatically ahead of all the initial delegates.

We will start a new thread for when we have the GUI ready for everyone to properly start delegate campaigns. This is a good chance to start positioning yourselves to succeed in the scramble for delegate positions when we launch the real thing. Enterprising technical users might start figuring out how to offer their services to non-technical users.

Let's begin!

* Step 1 **REQUIRED**: Open this in another tab   https://www.youtube.com/watch?v=Z-TOHc7I1pc

* Step 2: Wipe all your old data-dirs. Note that you might have both  ~/.BitSharesXTS  and  ~/BitShares\ XTS  - kill them all.

* Step 3: Pull latest and build.

* Optional Step 4:  If you are an initial delegate and a good citizen, do what you did before (import old private keys, make sure to wallet_enable_delegate_block_production). Details are sparse on purpose, since you probably want to skip this and go straight to 5.

* Step 5: Follow this guide: https://github.com/BitShares/bitshares_toolkit/wiki/DPOS-Registering-Names-And-Delegates

You will notice that you need funds to register your name / register as delegate. You have two options:
* import a key with funds
* ask someone nicely

This is the tech support thread. We'll open another related to delegate campaigns in the next day or two.

Edit: Blocks will be reaaaal slow near the start. Initial delegates, get online!

169
General Discussion / Names for dry run 3
« on: June 18, 2014, 03:28:39 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".

170
General Discussion / Better picture of the development team
« on: June 17, 2014, 12:33:37 am »

171
General Discussion / Dry Run 2: The Real Deal
« on: June 12, 2014, 11:24:02 pm »
We'll use this chain for voting for initial delegates for the real launch (assuming nothing goes wrong). Keep your shares if you want to have a say in who the initial delegates are.

Of course we cannot expect delegate campaigns to start or the masses to start voting until our GUI is ready. We'll start a separate thread for that, with pretty pictures. Soon.

Initial delegates, do this: https://github.com/BitShares/bitshares_toolkit/wiki/DPOS-initial-delegate-setup

Note that we removed some delegates for this round due to inactivity (or rather, inactivity as seen on our fork).
You can check if yours were the ones we removed here:
https://raw.githubusercontent.com/BitShares/bitshares_toolkit/master/libraries/blockchain/genesis.json


Notes
* All delegates were registered with "init-delegate-N" as names, this is expected. These are pre-registered accounts and you do not need to make new
* for people trying to get this to work on debian and getting import errors for keys, make sure that you compile with gcc 4.8, as gcc 4.7 doesn't work (compiles correctly but then crashes randomly or fails importing keys in weird places...)

172
General Discussion / Dan and Nikolai visit Virginia Tech to talk about Voting DAC
« on: June 12, 2014, 10:38:05 pm »
Sorry for poor video quality - we were not expecting that we would record and they just offered a little camera right before we started.

https://www.dropbox.com/s/eai0xp2x1l3or48/BitShares%20Voting%20Application.mp4

Our audience included members of Follow My Vote, Virginia Tech's engineering department, and NuSpark startup incubator.

173
KeyID / .p2p intro video - first draft - feedback wanted!
« on: June 11, 2014, 03:24:53 am »
* We will use a different voice actor (female voice from this video: https://www.youtube.com/watch?v=j5BjVn0nb4o )
* We have time to tweak the script

https://www.youtube.com/watch?v=w_l6iorlLhk

mirror: https://vimeo.com/97894638
pass = bitshares

Feedback?
Known issues:
* "auction" scene is a bit unclear
* some timings are a bit awkward

174
General Discussion / Delegates, start your engines!
« on: June 09, 2014, 01:54:36 am »
Here is the setup guide: https://github.com/BitShares/bitshares_toolkit/wiki/DPOS-initial-delegate-setup

Use this thread for issues related to getting your initial delegate running.

COMMON ISSUES, PLEASE READ:
* All delegates were registered with "init-delegate-N" as names, this is expected. These are pre-registered accounts and you do not need to make new accounts for anything, unless you want to.
* "wallet_list_receive_accounts" clips your names... for now type "enable_raw" before using your command to see the raw json dump with your names, I will fix the display tomorrow.
* for people trying to get this to work on debian and getting import errors for keys, make sure that you compile with gcc 4.8, as gcc 4.7 doesn't work (compiles correctly but then crashes randomly or fails importing keys in weird places...)

175
General Discussion / Delegates: need seed nodes for test net
« on: June 08, 2014, 05:04:41 pm »
These would be nodes that need high uptime but are NOT delegate nodes and don't have huge bandwidth requirements

Need IP and port

176
General Discussion / Initial delegates, let's get ready!
« on: June 07, 2014, 06:56:49 pm »
You *must* participate in the next test network to be an initial delegate. This will be a complete dry run with the correct genesis block.

We will pick delegates as soon as enough qualified people have followed these steps - don't put this off!

Ok guys stop saying "reserved" because this gives us no indication of if or when you will actually do it. This isn't the "candidate billboard" thread.

Please do these steps:

1) Make sure you are able to install and run the command-line client. You will find instructions in the github repo:
https://github.com/nmushegian/bitshares_toolkit/blob/master/BUILD_UBUNTU.md
https://github.com/nmushegian/bitshares_toolkit/blob/master/BUILD_OSX.md
https://github.com/nmushegian/bitshares_toolkit/blob/master/BUILD_WIN32.md

2) Set up your dedicated node. Tell us:
* Your IP and port ONLY IF you want to be a seed node (good chance to flex your delegate muscles if you can withstand DDOS)
* Your node's specs
* Your node's geographic location

3) Generate up to five keys. Use the utility at bitshares_toolkit/programs/utils/bts_create_key

Share with us the *public key* (not address)
Keep the *private key WIF format* (not the plain private key - actually keep both, WIF is just what you import)

For example:

toast-delegate-1 :  XTS76f6d9qrsvYJjv3ycbWWihaZyYBNCjCmLDoKHrPTooJKCQKBtD
toast-delegate-2 :  XTS6Sq54D8dNXRWeR9TLtMX4VqKDqfrQXBpC5dUkKA2ayrmUZVi2u


(and keep (do not share!) the ones that look like: 5HvMYtvvqrfBbP7GkFHHPPFCW4RfEftknj9mqHCvipEcgfecK8E )


We will choose a diverse set of initial nodes for this test network. The real test network will use whichever delegates are active at the end of this test. This means if your node goes offline during testing, you could get voted out and lose your spot! Likewise, if you are late to the party but convince people to vote you in, you could be an initial delegate.

Once again, being an initial delegate doesn't mean much because you still have to stay voted in.

To load your delegate key into the wallet do this:
Code: [Select]
wallet_add_contact_account your-delegate-1 XTS6VeDfUq4kT37yzWJs5stJEM3F11i1v6xghQBZYrFENp4aE843y
wallet_import_private_key ${PRIVATE_KEY FOR XTS6VeDfUq4kT37yzWJs5stJEM3F11i1v6xghQBZYrFENp4aE843y}

177
LottoShares / Check your expected LottoShares balance for AGS
« on: June 05, 2014, 07:28:13 pm »
http://pastebin.com/u9WKpcAb

You should multiply your AGS balance by (1000/152).

The total is off (too low) by about 400 lottoshares, or 0.004%. I think this is rounding, but it also might be because of keyhotee founder nonsense - unlike the rest of AGS this does not have an easily auditable definition and depends on the spreadsheets maintained by stan/danN  + my postprocessing being right. So worst case some founder gets less lottoshares than they should.

All my balances for "normal" AGS are right.

My personal opinion is that if everyone who checks it in this thread say it's OK, we should say "screw it, good enough" and not make FreeTrade waste any more time on this. We will provide a super-sure triple-checked AGS balance list for other DAC devs in the future.

178
General Discussion / [OVER] new testnet *WITH GUI! WOW!* inside
« on: June 04, 2014, 11:39:57 pm »
You know the drill!
Wipe your data-dir. Reconnect.

We have a single web wallet online for everyone to access. You can send to/from the web wallet from your CLI wallet. Don't be a dick and empty the wallet!
I repeat: YOU CAN SEND YOURSELF FUNDS WITHOUT HAVING TO ASK US
Advanced users can try running their own copy locally.
When we release the real client, it will be this web wallet wrapped in a Qt thing so you will have the usual one-click local app launch experience.

Don't create an account with a name that is pre-registered. We don't have "rename" enabled yet, and the client will not let you send when it is ambiguous (local contact "nikolai" or registered contact "nikolai"?)

http://162.243.127.243:9989/
username: a
password: a
wallet password: defaultpass


179
General Discussion / [OVER] New testnet iteration
« on: June 03, 2014, 10:32:04 pm »
Every time there is a hard-fork we will make a new thread so people know they have to resync and can ask for new funds.


Quote from: bytemaster on June 03, 2014, 10:10:49 pm
It has been an incredibly productive day of bug fixing

Quote
Known Issues:
1) Delegate Fee Registration not Enforced on Update
2) Wallet may not include enough fees in some cases
3) Sometimes wallet will attempt to vote for an invalid delegate (0)
4) Wallet cache of name updates may get out of sync (not reporting contacts as registered or delegates)
The known issues will likely be resolved in the next 24 hours...

We have resolved all of these issues which means that we have to reset the chain because of #2... there are now invalid transactions (that did not pay enough fees) in the chain which will prevent users with the latest code from syncing.   

We have also made a whole host of usability enhancements to the CLI.     A new chain will be launching shortly.
Quote from: bytemaster on June 03, 2014, 10:28:24 pm
If you relaunch the client with --clear-peer-database and --resync-blockchain  while running the latest code then you can keep your current wallet and contacts.

The wallet will still have a bunch of your stale transactions... which we need to clear out.    We will get something to do that tomorrow.

New chain is up with a new genesis block to prevent people from accidentally connecting to an invalid network.

Run this command to make sure you have the latest genesis block.
Quote
default (unlocked) >>> blockchain_get_config
  "blockchain_id": "fad10934fe03db46d4cd1934a47845d5080059933df3770ff6558abb764864e2",

180
General Discussion / MOVED: ProtoShares now on coinwik.or
« on: May 31, 2014, 10:42:57 pm »
This topic has been moved to Other Projects.

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

Pages: 1 ... 5 6 7 8 9 10 11 [12] 13 14 15 16 17 18 19

Page created in 0.181 seconds with 21 queries.