-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: SetFreezeTickSize #2769
Comments
I can see the use for the feature described in #2768, although even then, if an issuer changed their transfer rate and I didn't agree with the change, I could simply choose to send the funds back to them (transfers back to the issuer have an effective rate of 0, see here and here) But I'm not sure I see a benefit here. A tick size only affects the granularity of offers on the order books. I don't know why we'd want to prevent an issuer from changing that: it can be an advantage. In the absence of a compelling explanation about why this feature is necessary, I'm inclined to say that this feature doesn't really add enough functionality to justify the cost associated with it. Can you explain your rationale? |
My original concept with the economics of a Ripple-based Real Cash Economy Game is based upon the following from https://forum.ripple.com/viewtopic.php?f=1&t=9305
And the content from https://forum.ripple.com/viewtopic.php?f=23&t=9304
As the original plan is that the players are aware that at a very specific time each day/week/month that the issuer is going to programatically post 4 OfferCreate transactions (if Codius was feasible, I would use a smart contract to perform this task) an these transactions may in fact not be completely filled upon submission, so an opportunity may arise to progress further in the game by purchasing/trading for them with XRP/Issuances of the Game. This is also why a maximum supply of assets is not feasible within my use case, although I do very much appreciate the work-around that you provided in the other issue's thread. I hope now that all of you can see what I am attempting to do; I want to guarantee to players of this RCE Game that these offers' values' have consistency, so I must have the TickSize always set to 0-4 to ensure this consistency, and be able to a promise to my players cryptographically that this cannot change upon the operators' whim. ...Why will Ripple Inc not take me seriously when I say that you guys absolutely have to do a partnership of some sort with Mindark, the creators of DeepToken (DTA) and Entropia Universe ? Please tell me why you haven't done some kind of affiliation yet..? Y'know, after my agreement with Ripple Inc in 2016, if I did not feel that it would be absolutely and 100% morally wrong to speculate with the very, very large amount of XRP I was given but instead used it for its intended purpose to transfer value into my national fiat currency at the exchange rate of below 1 cent CAD each XRP... If I had chosen not too then I would definitely have the capital to approach Mindark myself to become a Planet Partner and I would not need you guys anymore but as it stands I do, so I am still here, still working. I hope all of you reading this post appreciate this content & my other feature request now that you have the full background of information available to you. Karlos, if you so happen by this issue, please unban me on XRPchat `so that I can participate in this and many other threads that require my attention & input. |
Closing due to inactivity. If anyone is still interested in this, please re-open, or open a new issue. |
Based on #2768 I would like for the team to please take under consideration that some use cases will require an AccountSet transaction where you may choose to set a flag of an issuing account in-so-that it may not change its TickSize once it is set.
The text was updated successfully, but these errors were encountered: