BitShares 2.0.151101 released

[twitter]

bue "1.6.25" updated . thanks for having chance to serve  our community 

[GChicken]

The Light wallet in this release fixed a few issue i was having with connections to Websocket on startup  much better experience!

Cheers 

[maqifrnswa]

I'm trying to download bitshares 2.0 for the first time for windows.

The cli-tools.exe / light. dmg / light.exe /  light.deb

Which one do I download?

Welcome!

Most likely light.exe

cli-tools.exe are useful for setting up your own full node
light.exe is the light wallet

light.dmg is the apple version
light.deb is the linux version

you can also use https://openledger.info/ instead of the light wallet

[bitAndy]

I'm trying to download bitshares 2.0 for the first time for windows.

The cli-tools.exe / light. dmg / light.exe /  light.deb

Which one do I download?

[lafona]

delegate-1.lafona delegate and seed node updated

[Tuck Fheman]

Pardon my ignorance, but is this the release that allows editing of UIA's in the GUI?

If not, where is that release?

It is.

In account page, go to assets then click on Update asset button for your asset.

A couple more stupid questions ...

What is "Market Fee" and "Max Market Fee", how are they used and what would be a proper setting (currently 0)?

And it shows a 1,000 BTS fee to update an asset, is that correct?  Seems a little high to edit an asset.

Thanks!

[maqifrnswa]

updated yesterday, don't know if anyone is keeping track so i'll post here

[roadscape]

roadscape updated

[checkrasier]

Thanks!  I could only see that right panel when the window was maximized.

[svk]

Pardon my ignorance, but is this the release that allows editing of UIA's in the GUI?

If not, where is that release?

It is.

In account page, go to assets then click on Update asset button for your asset.

[svk]

In this release of the light client selecting the "Trade" tab keeps taking me to that last market viewed and not the market selection page. Even closing and reopening light client still returns me to last market viewed. Is there another way to get to the market selection screen?

Same behavior using openledger or local host api connection.

Explore -> Markets, or "More markets" button below the market history.

[Xeldal]

In this release of the light client selecting the "Trade" tab keeps taking me to that last market viewed and not the market selection page. Even closing and reopening light client still returns me to last market viewed. Is there another way to get to the market selection screen?

Same behavior using openledger or local host api connection.

I agree, pretty confusing. Please consider changing back to what it was.

checkrasier, the way is:
Explore -> Markets

You can also get there from Trade tab, bottom right, where you switch between markets.  There is a button "More Markets"

 

[Tuck Fheman]

Pardon my ignorance, but is this the release that allows editing of UIA's in the GUI?

If not, where is that release?

[tonyk]

In this release of the light client selecting the "Trade" tab keeps taking me to that last market viewed and not the market selection page. Even closing and reopening light client still returns me to last market viewed. Is there another way to get to the market selection screen?

Same behavior using openledger or local host api connection.

I agree, pretty confusing. Please consider changing back to what it was.

checkrasier, the way is:
Explore -> Markets

[checkrasier]

In this release of the light client selecting the "Trade" tab keeps taking me to that last market viewed and not the market selection page. Even closing and reopening light client still returns me to last market viewed. Is there another way to get to the market selection screen?

Same behavior using openledger or local host api connection.

[liondani]

updated to BitShares 2.0.151101 and waiting for your votes....

If you want more security and more diversity for bts2 consider to vote for witness "liondani" 
I had two delegates in my control on bts1, delegate.liondani & jcalfee1-developer-team.helper.liondani

get_witness liondani
{
  "id": "1.6.48",
  "witness_account": "1.2.376",
  "last_aslot": 0,
  "signing_key": "BTS6zT2XD7YXJpAPyRKq8Najz4R5ut3tVMEfK8hqUdLBbBRjTjjKy",
  "vote_id": "1:59",
  "total_votes": "2437779856840",
  "url": "https://bitsharestalk.org/index.php/topic,6406.msg245698.html#msg245698",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}

[Xeldal]

xeldal updated

[Fox]

fox updated

[triox]

triox-delegate updated

[ffwong]

dragonball updated

[taoljj]

delegate.taolje is updated.

[wackou]

wackou updated

[alt]

delegate.baozi updated

[bitacer]

thank you

[tonyk]

Right , am I the only one having this issue though . The menu items became non-responsive.

Nope you are not the only one.
I am having the same/similar issues. Check the tech support subsection (or wherever this gui feedback thread is,)

[bitacer]

There is no need to upgrade light and web wallets.  Those hosting the api servers (ie full nodes) will need to update.

   
I did , what now ?

There is nothing you need to do.  The update by the servers is backend and is transparent to the users (ie you).

Right , am I the only one having this issue though . The menu items became non-responsive.

[cube]

There is no need to upgrade light and web wallets.  Those hosting the api servers (ie full nodes) will need to update.

   
I did , what now ?

There is nothing you need to do.  The update by the servers is backend and is transparent to the users (ie you).

[bitacer]

There is no need to upgrade light and web wallets.  Those hosting the api servers (ie full nodes) will need to update.

   
The web one I cant update anyway. At one point on an account view all menu links become non-responsive.

[cube]

There is no need to upgrade light and web wallets.  Those hosting the api servers (ie full nodes) will need to update.

[bitacer]

Is there a glitch ,  menu links get stuck . They dont work neither on light wallet nor web wallet

[Marketorder]

Do I have to update my Light Wallets constantly? I just updated my wallet when 2.0 came out what if I don't update again?

[mindphlux]

Updated my witness node.

[Musewhale]

nice

[Thom]

I count 12 reports of updates so far. I hope by the end of the day tomorrow we'll see 31 here.

[cube]

bitcube updated.

[rnglab]

rnglab updated

[Thom]

Verbaltech updated witness and all seed nodes.

[abit]

in.abit updated.

[Bhuz]

bhuz updated

[clayop]

delegate-clayop updated

[checkrasier]

witness checkraiser is updated

[boombastic]

mr.agsexplorer updated

[ElMato]

ElMato updated

[clayop]

When does the refund feature take effect?

[spartako]

Spartako updated

[theoretical]

Will it be a problem to deploy this or do you plan to add other items later today?

If you plan on updating this again today I'll wait.

No, I tested it extensively, and hopefully our next upgrade will not be for a while.  We've heard the cries of people who don't like to have to upgrade constantly.  So we're trying to better organize our development process and do more internal testing of new releases to hopefully make it a thing of the past to have cycles of the form "release hardfork, discover hardfork has problems, release another hardfork to correct problems in first hardfork."

[pc]

Upgraded witness cyrano.

[Thom]

Sorry the version number is a day off, I goofed entering the date.

Will it be a problem to deploy this or do you plan to add other items later today?

If you plan on updating this again today I'll wait.

[theoretical]

Sorry the version number is a day off, I goofed entering the date.

[theoretical]

The release is available at https://github.com/bitshares/bitshares-2/releases/tag/v2.0.151101

All full nodes will need to upgrade to this release by Wed Nov 4 16:00:00 UTC 2015.

• Corrects an issue in the previous release that prevents PARENT.CHILD assets from being created #409
• Add the capability for asset owner to claim asset fees #413
• Allow asset issuers to blacklist some accounts from holding a particular asset while maintaining a "default accept" policy for other accounts #415

In addition, numerous bug fixes and wallet enhancements have been included, and reindexing performance has been improved.

Reindexing will be required, and should occur automatically.

EDIT:  If you run a MUSE node, you will need to update MUSE release as well, see https://github.com/peertracksinc/muse/releases/tag/v1.0.151101