1000 BTS fee to update an asset?!

[svk]

No you're not screwed don't worry. The easiest way to set the CORE exchange rate is to use integers, or at least numbers larger than 1. So if you want 0.01 TIPSHARES/BTS, set BTS to 100 and TIPSHARES to 1.

@tonyk I'm not sure what you're referring to, but if you're missing permissions and flags its because they were not enabled upon creation and you cannot enable them afterwards.

[tonyk]

I am not even close to seeing that many fields...and I am on OL with IE  and Chrome.

Once again - do I have to create the UIA first, in order to see them?

I think so man. I don't remember seeing them until the ability to edit these settings were put into the new lightwallet.

Thanks man!

Can you hit - "Create Asset" for me, when you have time, to see if they indeed disappear for new asset creation. Thanks.

[Tuck Fheman]

You're using an old version, there was an update yesterday that changed that page quite a lot. Try refreshing if you're using openledger, or download the new client if not.

Aww damn. I checked the repository before I went to bed, it must have been uploaded afterwards. OK will grab the new one and check it out.

Ninja edit : The latest version on GitHub is the one I'm using. It was uploaded 10 days ago. "BitShares 2.0.151111"

Or am I on the wrong page? ... https://github.com/bitshares/bitshares-2/releases

Also, you cannot enter more decimals than the precision of your asset, which was set on creation.

DOH! So there's no way to change this after creation?

Also, tony's image from OL shows the flags you can set, but those are not present in the latest lightwallet.

Ninja edit #2: If I set CER to 0.001 it accepts that setting but only displays 0.00 (mentioned above), however if I try to update the asset clicking the UPDATE button does nothing. If I set it to 0.01 it will allow me to update. So I'm going to assume that has to do with what you stated previously, when we created the asset we must have set the precision to 0.00 (two decimal places) which is causing this, is that correct? If the precision is un-editable after creation I guess we're kind of screwed and this asset is useless(?).

Thanks for all the help!!!

[Tuck Fheman]

I am not even close to seeing that many fields...and I am on OL with IE  and Chrome.

Once again - do I have to create the UIA first, in order to see them?

I think so man. I don't remember seeing them until the ability to edit these settings were put into the new lightwallet.

[tonyk]

I am not even close to seeing that many fields...and I am on OL with IE  and Chrome.

Once again - do I have to create the UIA first, in order to see them?

[svk]

Quote & base amounts set the Core Exchange Rate, which determines the fees. Try 1 TIPS : 4 BTS.

For example if an xfer costs 40 BTS and the CER is 4 BTS/TIPS, then the xfer fee can be paid with either 40 BTS or 10 TIPS.

Assuming the market value of 1 TIPS is around 4 BTS:
If you want to make money off transfers, set the CER lower than market value (e.g. 1 BTS/TIP). You'll make profit off the fee pool.
If you want to subsidize transfers, set the CER above market value (e.g. 40 BTS/TIP). You'll have to refill the fee pool more often.

Thanks! I'm still not clear on what all that means or rather how to accomplish it in the GUI, but this stuff is not my strong point in life. 

You also need to enable the flag for Charge Market Fee, looks to me like it's set to off right now.

Your current core exchange rate is 1000 TIPSHARES/BTS, so I guess the fee pool conversion will charge 40,000 TIPSHARES  for a transfer.

Where do I "enable the flag"?

Here's what the settings are now that are yielding undesirable results.



Swapping to TIPSHARES/BTS (which I didn't notice before I could do) made this a little clearer.

*BUG*  ?
However please note that the Quote Asset Amount field will only allow 3 digits to be entered. It's seems to be registering the fact that I've entered a 4th digit (but does not allow more than that), but the 4th digit is not displayed in the GUI. In the image below I have entered 0.001, but it's only displaying 0.00 and I can't bring it below 100/1 TIPSHARES/BTS.

You're using an old version, there was an update yesterday that changed that page quite a lot. Try refreshing if you're using openledger, or download the new client if not.

BTW the price is now 20 BTS to update an asset. Also, you cannot enter more decimals than the precision of your asset, which was set on creation.

[Tuck Fheman]

Quote & base amounts set the Core Exchange Rate, which determines the fees. Try 1 TIPS : 4 BTS.

For example if an xfer costs 40 BTS and the CER is 4 BTS/TIPS, then the xfer fee can be paid with either 40 BTS or 10 TIPS.

Assuming the market value of 1 TIPS is around 4 BTS:
If you want to make money off transfers, set the CER lower than market value (e.g. 1 BTS/TIP). You'll make profit off the fee pool.
If you want to subsidize transfers, set the CER above market value (e.g. 40 BTS/TIP). You'll have to refill the fee pool more often.

Thanks! I'm still not clear on what all that means or rather how to accomplish it in the GUI, but this stuff is not my strong point in life. 

You also need to enable the flag for Charge Market Fee, looks to me like it's set to off right now.

Your current core exchange rate is 1000 TIPSHARES/BTS, so I guess the fee pool conversion will charge 40,000 TIPSHARES  for a transfer.

Where do I "enable the flag"?

Here's what the settings are now that are yielding undesirable results.



Swapping to TIPSHARES/BTS (which I didn't notice before I could do) made this a little clearer.

*BUG*  ?
However please note that the Quote Asset Amount field will only allow 3 digits to be entered. It's seems to be registering the fact that I've entered a 4th digit (but does not allow more than that), but the 4th digit is not displayed in the GUI. In the image below I have entered 0.001, but it's only displaying 0.00 and I can't bring it below 100/1 TIPSHARES/BTS.

[tonyk]

Is the GUI supporting some random parts of UIA controls and settings?

I see no "Max Market Fee" and or "Core Exchange Rate"/"CER"

I know it is a work in progress. Just confirming that I do not to first create the asset, to be able to see those  things?

[svk]

I edited the Market Fee % of the UIA to 0.01%.

When I try to send some it's charging a fee of over 42,000 of the UIA.

I set the Max Market Fee to 10.

How do I make the UIA only charge around 1 of the UIA with a max of 10 to transfer?

Another question is what do the Quote Asset Amount and Base Asset Amount fields do?

Thanks!

You also need to enable the flag for Charge Market Fee, looks to me like it's set to off right now.

Your current core exchange rate is 1000 TIPSHARES/BTS, so I guess the fee pool conversion will charge 40,000 TIPSHARES  for a transfer.

[roadscape]

I edited the Market Fee % of the UIA to 0.01%.

When I try to send some it's charging a fee of over 42,000 of the UIA.

I set the Max Market Fee to 10.

How do I make the UIA only charge around 1 of the UIA with a max of 10 to transfer?

Another question is what do the Quote Asset Amount and Base Asset Amount fields do?

Thanks!

Quote & base amounts set the Core Exchange Rate, which determines the fees. Try 1 TIPS : 4 BTS.

For example if an xfer costs 40 BTS and the CER is 4 BTS/TIPS, then the xfer fee can be paid with either 40 BTS or 10 TIPS.

Assuming the market value of 1 TIPS is around 4 BTS:
If you want to make money off transfers, set the CER lower than market value (e.g. 1 BTS/TIP). You'll make profit off the fee pool.
If you want to subsidize transfers, set the CER above market value (e.g. 40 BTS/TIP). You'll have to refill the fee pool more often.

[Tuck Fheman]

I edited the Market Fee % of the UIA to 0.01%.

When I try to send some it's charging a fee of over 42,000 of the UIA.

I set the Max Market Fee to 10.

How do I make the UIA only charge around 1 of the UIA with a max of 10 to transfer?

Another question is what do the Quote Asset Amount and Base Asset Amount fields do?

Thanks!

[Tuck Fheman]

Did you pay the "typing fee" upfront?

It was feature available on blockchain level only...but now svk screwed a potential great revenue stream for BTS.

PS
I think if you pay the "typing fee", the long name creation fee - this a fee for creating non-premium names cause they tend to be longer than the more expensive premium names, and the transaction size fee you will have no problems. Well definitely in more cases than not.

https://youtu.be/d2nM55ko_ys

[tonyk]

I finished that part but now a new issue has cropped up. When I click "Issue Asset" it will only allow me to enter certain letters in the "Issue to" field. I can enter "tu" but cannot go any further with "c". But if I put an "e" it will take it (not that I want to lol) and then it just stops letting me enter any more letters. Is this a bug?

Did you pay the "typing fee" upfront?

It was feature available on blockchain level only...but now svk screwed a potential great revenue stream for BTS.

PS
I think if you pay the "typing fee", the long name creation fee - this a fee for creating non-premium names cause they tend to be longer than the more expensive premium names, and the transaction size fee you will have no problems. Well definitely in more cases than not.

[Tuck Fheman]

I finished that part but now a new issue has cropped up. When I click "Issue Asset" it will only allow me to enter certain letters in the "Issue to" field. I can enter "tu" but cannot go any further with "c". But if I put an "e" it will take it (not that I want to lol) and then it just stops letting me enter any more letters. Is this a bug?

Yep looks like you found a bug, I'll have a look.

Fixed here: https://github.com/cryptonomex/graphene-ui/commit/7a7240ec4cafe772b81caa3e7a668b2eb4c7ede6

I've asked Valentine if he can do another update today to push this fix, we'll see.

Cool thanks!

[svk]

I finished that part but now a new issue has cropped up. When I click "Issue Asset" it will only allow me to enter certain letters in the "Issue to" field. I can enter "tu" but cannot go any further with "c". But if I put an "e" it will take it (not that I want to lol) and then it just stops letting me enter any more letters. Is this a bug?

Yep looks like you found a bug, I'll have a look.

Fixed here: https://github.com/cryptonomex/graphene-ui/commit/7a7240ec4cafe772b81caa3e7a668b2eb4c7ede6

I've asked Valentine if he can do another update today to push this fix, we'll see.