BitShares Forum
Main => General Discussion => Topic started by: bytemaster on August 04, 2015, 02:32:44 pm
-
https://graphene.bitshares.org/
There are still bugs all over the place in the wallet. This isn't an official test net by any stretch of the imagination.
We are still working out kinks in the wallet import functionality.
-
Much cooler domain:
==> http://test.the.decentral.exchange
:P
I like the wallet ... react-js makes it extremely slick to use! Well chosen.
Hurry to the webdevs!!
-
Blank screen on my ipad
-
Blank screen on my ipad
It's not yet compatible to most mobile browsers I fear ...
Have you tried with chrome?
//edit:
BTW: head block #316,998 ... 1 sec block interval!!!
-
Blank screen on my ipad
It's not yet compatible to most mobile browsers I fear ...
Have you tried with chrome?
yep currently not working on mobile devices .. like iphone or android..same for me ..blank screen
Anyway great work !!
-
https://bitshares.org/blog/2015/08/04/howto-become-a-witness/
-
Looks cool and it's fast and responsive.
Really well done :)
-
Looks cool and it's fast and responsive.
Really well done :)
This statement form your side counts much :) !! Didn't you create wallet GUI with dark attitude before months also!? I do remember that have a lot of good ideas about UX improvements. I begin to think maybe it would be godd if you would join the GUI discussion better to say ... i would love to get feedback from you about UX improvements etc..
Where are you located ... if i may ask? Europe ?
-
It's great to be able to see progress and test it. Looks good as well!
How safe is this to use without 2FA or hardware wallets and will they be implemented?
-
How safe is this to use without 2FA or hardware wallets and will they be implemented?
2FA is planned .. hardware wallets ... we will see later on too i begin to think but not for the launch AFAIK!
-
I can't see anything on my iPhone, so I will have to wait until I get home.
Looking forward to seeing it. Sounds like it looks good :)
I'm assuming that it will be compliant with iPad/iPhone when we go live right?
-
I can't see anything on my iPhone, so I will have to wait until I get home.
Looking forward to seeing it. Sounds like it looks good :)
I'm assuming that it will be compliant with iPad/iPhone when we go live right?
iPhone / iPad support is VERY high priority.
-
I'm assuming that it will be compliant with iPad/iPhone when we go live right?
AFAIK there is work been done to get this implemented in a native app ..
-
Wow.. the site is out. Because of too many accesses?
-
very nice but..
For what is worth:
I have created an account, was able to see core balance, exchange, delegates, witnesses etc very nicely.
Then I have locked the wallet and when I tried to unlock, although it has succesfully unlocked I don't see any balances, exchange pairs, delegates ..nothing..
-
very nice but..
For what is worth:
I have created an account, was able to see core balance, exchange, delegates, witnesses etc very nicely.
Then I have locked the wallet and when I tried to unlock, although it has succesfully unlocked I don't see any balances, exchange pairs, delegates ..nothing..
You should check the connection. The wallet is out of order now.
-
can't establish a connection to the server at wss://graphene.bitshares.org:8090/
-
great news. how to setup the testnet or connect to testnet?
-
great news. how to setup the testnet or connect to testnet?
Would be good to have a set of seed nodes already ..
-
Keeps failing creating an account.. I guess corporate firewall issues. Ill check it later.
-
Keeps failing creating an account.. I guess corporate firewall issues. Ill check it later.
required port for websocket is 8090 ..
-
I can't see anything on my iPhone, so I will have to wait until I get home.
Looking forward to seeing it. Sounds like it looks good :)
I'm assuming that it will be compliant with iPad/iPhone when we go live right?
iPhone / iPad support is VERY high priority.
That's very good news. Thank you by remaster :)
-
Keeps failing creating an account.. I guess corporate firewall issues. Ill check it later.
Probably because the hosted wallet is down. Check block number in right-bottom corner first.
-
Keeps failing creating an account.. I guess corporate firewall issues. Ill check it later.
required port for websocket is 8090 ..
Correct, I have just seen the error "WebSocket connection to 'wss://graphene.bitshares.org:8090/' failed: Error in connection establishment: net::ERR_TIMED_OU"
-
Correct, I have just seen the error "WebSocket connection to 'wss://graphene.bitshares.org:8090/' failed: Error in connection establishment: net::ERR_TIMED_OU"
it seems the websocket daemon went down under the load :D
-
Very snappy and responsive!
One thing I noticed is that when I got to the "Accounts" Section... it only shows me 1 page, and they all start with the same letter as my account. I can't display any other pages with different accounts.
-
chrome console log:
Download the React DevTools for a better development experience: https://fb.me/react-devtools
app.js:27 WebSocket connection to 'wss://graphene.bitshares.org:8090/' failed: Error during WebSocket handshake: Unexpected response code: 502
app.js:27 !!! WebSocket Error wss://graphene.bitshares.org:8090
app.js:1 [App.jsx] ----- ERROR -----> Event undefined
10app.js:75 Uncaught TypeError: Cannot read property 'exec' of undefined
app.js:130 Congratulations, your wallet was successfully created.
https://graphene.bitshares.org/api/v1/accounts Failed to load resource: the server responded with a status of 422 (Unprocessable Entity)
app.js:130 ERROR AccountActions.createAccount Objectbase: Array[1]0: "some backend error"length: 1__proto__: Array[0]__ARRAY__: trueconcat: function concat() { [native code] }constructor: function Array() { [native code] }copyWithin: function copyWithin() { [native code] }entries: function entries() { [native code] }equals: function (e){if(!e)return!1;if(this.length!==e.length)return!1;for(var t=0,n=this.length;n>t;t++)if(this[t]instanceof Array&&e[t]instanceof Array){if(!this[t].equals(e[t]))return!1}else if(this[t]!==e[t])return!1;return!0}every: function every() { [native code] }fill: function fill() { [native code] }filter: function filter() { [native code] }find: function find() { [native code] }findIndex: function findIndex() { [native code] }forEach: function forEach() { [native code] }includes: function includes() { [native code] }indexOf: function indexOf() { [native code] }join: function join() { [native code] }keys: function keys() { [native code] }lastIndexOf: function lastIndexOf() { [native code] }length: 0map: function map() { [native code] }pop: function pop() { [native code] }push: function push() { [native code] }reduce: function reduce() { [native code] }reduceRight: function reduceRight() { [native code] }reverse: function reverse() { [native code] }shift: function shift() { [native code] }slice: function slice() { [native code] }some: function some() { [native code] }sort: function sort() { [native code] }splice: function splice() { [native code] }toLocaleString: function toLocaleString() { [native code] }toString: function toString() { [native code] }unshift: function unshift() { [native code] }values: function values() { [native code] }Symbol(Symbol.iterator): function values() { [native code] }Symbol(Symbol.unscopables): Object__proto__: Object__proto__: Object
-
Still down? After clicking Create Account I only get "Loading.."
-
The backend node is offline which means that RPC requests can not be served. Valentine is currently flying back to VA from CA so is unable to fix that at this time.
Anyway, this wasn't an official test net. I just wanted to give a sneak peek on what we have under development.
-
Can anyone post instructions for what to do?
If I import to graphene, what happens to my BTS?
-
Correct, I have just seen the error "WebSocket connection to 'wss://graphene.bitshares.org:8090/' failed: Error in connection establishment: net::ERR_TIMED_OU"
it seems the websocket daemon went down under the load :D
https://youtu.be/BjR8l2ucdvs?t=2m28s
-
Can anyone post instructions for what to do?
Only instruction we have atm is about howto become a witness in graphene/bts2.0 (see bitshares blog)
If I import to graphene, what happens to my BTS?
nothing .. the two networks are INDEPENDENT .. much like an airdrop
-
It's back online.
Update: crashed again, we are investigating this..
-
Blank screen on my ipad
and my macbook pro
-
Blank screen on my ipad
and my macbook pro
This is because I stopped witness node until we resolve the issue.
-
Looks cool and it's fast and responsive.
Really well done :)
This statement form your side counts much :) !! Didn't you create wallet GUI with dark attitude before months also!? I do remember that have a lot of good ideas about UX improvements. I begin to think maybe it would be godd if you would join the GUI discussion better to say ... i would love to get feedback from you about UX improvements etc..
Where are you located ... if i may ask? Europe ?
Thank you, @cass.
Yes, early this year my company made an attempt to offer an improvement for BitShares UX - it was a JavaFX desktop application, fully functional and we were almost ready to release it but we hold off for two reasons:
(1) we decided we didn't have enough resources to offer proper technical support
(2) BitShares 2.0 was announced
For those interested, screenshots are still available here (http://consense.pl/bts/screens/).
We are an IT company located in Warsaw, Poland.
I'll be glad to get in touch with you, cass, as I really appreciate what you've done so far.
My only concern regarding the new BitShares GUI comes down to a technical limitation: as a web app it does not allow to split the GUI into separate pages, each keeping track of its own state.
The easiest way to explain it would be by this example: I'd like to be able to do some trading on the Exchange page, then go to my account transaction history page to check something and then go back to the Exchange page and see it exactly as I left it.
As far as I know such multi-tasking is not yet be possible in JavaScript.
-
My only concern regarding the new BitShares GUI comes down to a technical limitation: as a web app it does not allow to split the GUI into separate pages, each keeping track of its own state.
The easiest way to explain it would be by this example: I'd like to be able to do some trading on the Exchange page, then go to my account transaction history page to check something and then go back to the Exchange page and see it exactly as I left it.
As far as I know such multi-tasking is not yet be possible in JavaScript.
You can easily maintain state across multiple "tabs" in any good javascript app framework. You don't keep the data in the dom.
There's no true multi threading but nothing ever blocks either...
-
It seems to work just fine on Firefox for android.
-
It seems to work just fine on Firefox for android.
cool yes guess Safari is currently the problem ...AFAIK from SLACK dev group
-
It seems to work just fine on Firefox for android.
cool yes guess Safari is currently the problem ...AFAIK from SLACK dev group
Yah. My mistake. I thought people were saying they couldn't access on android. Seems to work fine on chrome for android as well.
-
Can anyone post instructions for what to do?
Only instruction we have atm is about howto become a witness in graphene/bts2.0 (see bitshares blog)
If I import to graphene, what happens to my BTS?
nothing .. the two networks are INDEPENDENT .. much like an airdrop
And can you do it now? I may be confusing things but what keeps someone from importing his BTS into graphene and then since he keeps his BTS on his wallet, send them to an exchange and dump for btc, doubling his money?
-
Ahhhh, awesome! These 1 second block times are making my head spin!
-
Ahhhh, awesome! These 1 second block times are making my head spin!
Is this just testing for private internal systems or is this really being considered a possibility for the public BTS blockchain?
-
Ahhhh, awesome! These 1 second block times are making my head spin!
Is this just testing for private internal systems or is this really being considered a possibility for the public BTS blockchain?
From bitshares.org:
"As soon as the software is ready, it will enter a public testing period for gathering community feedback. This testing period will last until the community is satisfied with the new system, after which an upgrade snapshot date will be announced with at least 30 days notice.
At the snapshot, the current BitShares network will stop producing blocks and BitShares 2.0 will be launched within hours. All accounts and balances will be fully migrated to BitShares 2.0.
See Migrating to BitShares 2.0 (https://bitshares.org/blog/2015/06/08/migrating-to-bitshares-2.0/) for more details."
-
Ahhhh, awesome! These 1 second block times are making my head spin!
Is this just testing for private internal systems or is this really being considered a possibility for the public BTS blockchain?
From bitshares.org:
"As soon as the software is ready, it will enter a public testing period for gathering community feedback. This testing period will last until the community is satisfied with the new system, after which an upgrade snapshot date will be announced with at least 30 days notice.
At the snapshot, the current BitShares network will stop producing blocks and BitShares 2.0 will be launched within hours. All accounts and balances will be fully migrated to BitShares 2.0.
See Migrating to BitShares 2.0 (https://bitshares.org/blog/2015/06/08/migrating-to-bitshares-2.0/) for more details."
Regarding the 1 second block times though?
-
Ahhhh, awesome! These 1 second block times are making my head spin!
Is this just testing for private internal systems or is this really being considered a possibility for the public BTS blockchain?
From bitshares.org:
"As soon as the software is ready, it will enter a public testing period for gathering community feedback. This testing period will last until the community is satisfied with the new system, after which an upgrade snapshot date will be announced with at least 30 days notice.
At the snapshot, the current BitShares network will stop producing blocks and BitShares 2.0 will be launched within hours. All accounts and balances will be fully migrated to BitShares 2.0.
See Migrating to BitShares 2.0 (https://bitshares.org/blog/2015/06/08/migrating-to-bitshares-2.0/) for more details."
Regarding the 1 second block times though?
From BitShares.org:
Delegated Proof of Stake Consensus (https://bitshares.org/technology/delegated-proof-of-stake-consensus/)
All network parameters, from fee schedules to block intervals and transaction sizes, can be tuned via elected delegates. Deterministic selection of block producers allows transactions to be confirmed in an average of just 1 second.
-
Ahhhh, awesome! These 1 second block times are making my head spin!
Is this just testing for private internal systems or is this really being considered a possibility for the public BTS blockchain?
From bitshares.org:
"As soon as the software is ready, it will enter a public testing period for gathering community feedback. This testing period will last until the community is satisfied with the new system, after which an upgrade snapshot date will be announced with at least 30 days notice.
At the snapshot, the current BitShares network will stop producing blocks and BitShares 2.0 will be launched within hours. All accounts and balances will be fully migrated to BitShares 2.0.
See Migrating to BitShares 2.0 (https://bitshares.org/blog/2015/06/08/migrating-to-bitshares-2.0/) for more details."
Regarding the 1 second block times though?
AFAIK, block time can vary from 1 sec to 30 sec (should check maximum) determined by delegates. I think 2 second will be starting point
-
2 second blocks means on average your transaction is confirmed in 1 second. 1 second blocks means an average confirmation in 0.5 seconds.
-
Looks very nice and fluid on Samsung Galaxy tab II with Chrome.
Nice work !!!!!
-
I've been having trouble importing a wallet that has 460 keys. The GUI only gives me the option to reset.
When trying to import another balance I get the following error:
Key import error: The transaction was aborted, so the request cannot be fulfilled.
-
For those interested, screenshots are still available here (http://neura.sx/bts/screens/).
This is some good work, i really like the look of your screenshots. I wonder if we can incorporate some of this to help polish the look ;)
The performance of 2.0 is night and day compared to the old wallet. +5%
-
Feels nice and responsive. (http://i.imgur.com/7drHiqr.gifv) Massive potential.. 1 second transactions is mind blowing.
I'd love to see the exchange as well, but whenever I click a market the wallet stops working?
-
This website is under heavy load
We're sorry, too many people are accessing this website at the same time. We're working on this problem. Please try again later.
-
This website is under heavy load
We're sorry, too many people are accessing this website at the same time. We're working on this problem. Please try again later.
Accesses by many Chinese people? :)
-
And here I thought I'd get some sleep tonight. Mnnope!
@Xeroc - Great writeup on how to get a witness up and running. Much appreciated.
-
I've been having trouble importing a wallet that has 460 keys. The GUI only gives me the option to reset.
When trying to import another balance I get the following error:
Key import error: The transaction was aborted, so the request cannot be fulfilled.
That's my fault most likely, I appear to have broken some of jcalfees import code when I refactored it..
-
Feels nice and responsive. (http://i.imgur.com/7drHiqr.gifv) Massive potential.. 1 second transactions is mind blowing.
I'd love to see the exchange as well, but whenever I click a market the wallet stops working?
Try flipping the markets, there's a bug related to the call orders that breaks the exchange, but its only in one market direction. Already fixed the bug but we need Valentine to update the wallet.
-
what a joke. still cant access
-
what a joke. still cant access
Read the first entry:
This isn't an official test net by any stretch of the imagination.
-
what a joke. still cant access
Seriously. Why is this pre alpha site exposed for early testing not stable? Amateur hour up in here.
-
If I create a wallet and then I lock it, close the page and revisit the web page it shows me my account. I hope this will not happen in the real thing.
Also if I clear cookies and history etc and I revisit the page i have to re create another wallet? I can't use the one I have created?
I am sure you are aware of these things, just thought to mention them just in case..
-
The US guys only just woke up, but James is looking into what happened to the server now.
-
If I create a wallet and then I lock it, close the page and revisit the web page it shows me my account. I hope this will not happen in the real thing.
Also if I clear cookies and history etc and I revisit the page i have to re create another wallet? I can't use the one I have created?
I am sure you are aware of these things, just thought to mention them just in case..
The wallet is stored in an IndexedDb in your browser, so if you clear that you delete the wallet. We will have brain key functionality for restoration later and we will make sure this is clear.
As long as you have a wallet you can browse around though so seeing your account without unlocking is normal, at least for now.. You will need to unlock before making transactions only.
-
I like the speed and the functionality. It's soo much faster than 1.0
If i'm being honest though, I think the 1.0 wallet looked more professional and polished.
That said, I know this GUI is still a work in progress ;)
-
Took it for a test drive yesterday.. very nice progress. Great job guys. +5%
-
what a joke. still cant access
@Krills - which browser and OS you're using..?
-
what a joke. still cant access
@Krills - which browser and OS you're using..?
I cannot access too. Probably the node is closed.
-
The node is down and the silence from the devs makes me think there is a problem, a big one.
-
The node is down and the silence from the devs makes me think there is a problem, a big one.
I'm so sad that the node is down. But dev team should focus on Graphene codework not on premature testnet. I will wait ;)
-
For those wondering about the witness howto: It moved to the github wiki:
https://github.com/cryptonomex/graphene/wiki/Howto-become-an-active-witness-in-BitShares-2.0
It seems some people interpreted the "blog post" as an official launch of BTS2 .. I appologize for that
-
I'm so sad that the node is down. But dev team should focus on Graphene codework not on premature testnet. I will wait ;)
Yes. The devs should prioritise the development and internal testing of Graphene. There is not much point in supporting end-user testnet when the underlying codes are not stable.
-
It was a few bugs in the c++ code... one to crash it and another glitch that prevented the restart.. we are investigating it. That's what testing is for, next one will be better!
-
It was cool while it lasted. Excited for the next iteration.
-
Wow.. the site is out. Because of too many accesses?
A good problem to have :)
-
It was a few bugs in the c++ code... one to crash it and another glitch that prevented the restart.. we are investigating it. That's what testing is for, next one will be better!
+5% +5%
-
It seems some people interpreted the "blog post" as an official launch of BTS2 .. I appologize for that
maybe just highlight this on a general warning or someting on the blog? Would this make sense!?
-
It seems some people interpreted the "blog post" as an official launch of BTS2 .. I appologize for that
maybe just highlight this on a general warning or someting on the blog? Would this make sense!?
I think it's ok to have it on the github wiki ..
We will need a page for technical documentation anyway .. and I'd love to have it like bitcoin.org does .. a simple markdown based wiki (jekyll)
-
It seems some people interpreted the "blog post" as an official launch of BTS2 .. I appologize for that
maybe just highlight this on a general warning or someting on the blog? Would this make sense!?
I think it's ok to have it on the github wiki ..
We will need a page for technical documentation anyway .. and I'd love to have it like bitcoin.org does .. a simple markdown based wiki (jekyll)
yep good idea