SunnyToes, we tried to voice your concerns to the devs and they are too busy to address it now. Perhaps you can come up with a technical proposal with real solutions to the problems you're concerned with. If you find a capable developer and can put together a well thought out, detailed, and accurate Polietia proposal, I would vote for it. Other than that I think you're now wasting your time... No offense. The answer from the developers was very clear - they are not going to focus on this issue. That means you can do it yourself, if you like. I agree with you that this is a problem, but I personally don't have the expertise or the time to solve it.
thanks david, but my time on slack is ... metered. certainly, I could put forth a proposal, but this is a bigger issue than any one should solve. it's gonna take a community, and I thought here may be a place to plant seeds. Also, I am unwilling to put forth a Pi proposal without a dev team to pull it off; i'm not trying to lay the work on somebody else. I don't think this concept is worth doing until it is developed further. you are right it needs more experts. I was hoping we could all ask questions of it until it improved to a presentable state.
if you cant contribute: dont talk or act. right? if you have a few braincells or DCR to contribute, let's get the convo moving, and quite asking others to do it for you. Posting Issues is like a bad case of 'liefpartner'. get over it. get too the work. If you are invested in the scope, get in the car, an either leave the door open or close it. That's action worth taking. Don't be so trigger happy on the name recognition and Issue posting, when you arent' contributing more than 2 atoms.
Ticket price is going up while DCR price is going down 😅 I expect the DCR returned from my next voted ticket won’t be enough to get me a new full ticket 🤦🏻♂️ It seems that the ticket price goes in an opposite direction with the DCR price??? Is my observation right??
Much appreciated 🙏 pretty high ROI imho. 28 days-voting cycle per ticket is it how random works? I'm concerned a little on the matter of how a ticket being selected? What are there chances for a single ticket to be chosen twice during 28 days and the opposite to be not chosen before expiring
The following instructions are for users of Decrediton and will walk you through getting setup for ticket splitting. To participate in ticket splitting, you must have: • A user account on on of the supported pools: DECREDVOTING.COM STAKE.DECREDBRASIL.COM • v0.6.2 of matheusd's ticket splitting software. • At least 5.0 DCRTo get started, follow these steps:1. Create an account with one of the pools and follow the account setup instructions for that pool.2. Download and extract the ticket splitting utility for your OS: • Windows 64-bit • Linux 64-bit • Mac3a. Run Decrediton and load your wallet. Make sure that Decrediton has sync'd to the latest block.3b. Run splitticketbuyergui from the package you just downloaded.4. Click the Config menu item in splitticketbuyergui and select "Load from Decrediton". Verify that the Vote Address and Pool Subsidy Address fields have populated as follows: • The vote address should begin with Dc and the Pool Subsidy Address should begin with Ds. • Also, verify that the Matcher Host shows the matcher from your selected pool. • Note: If you are running Ubuntu, you may need to specify the port number with the matcher host in the configuration file. Such a configuration would look like: :84755. Adjust the slider at the top of Split Ticket Buyer to the amount of DCR that you want to contribute to the ticket. Please note that the minimum you can participate with is 5 DCR! Also, note that the splittickerbuyer GUI will only let you contribute an integer. It is possible to contribute down to the hundredth's place by using the CLI version of split-ticket-buyer.6. Create a test session to make sure things work. (Make sure Decrediton is running and your wallet is loaded!) Note: To ensure that a ticket is not unintentionally funded, choose a random string of letters & numbers to use as the session name for this test. If you happen to enter the same session name as another user and there is enough combined DCR in the session to fully fund a ticket, the transaction will go through and both you and the other user will have purchased a split ticket. If you do not see any sessions in the Currently Waiting Sessions list at the bottom of this page then there are no open sessions and the risk is minimal. a. Enter a random Session Name b. Enter your wallet passphrase c. Click on Participate. Read and accept the disclaimer. d. The text window in the split ticket buyer should show: "Waiting participants (# DCR): [# DCR]" and your session should appear on this page below in the Currently Waiting Sessions section.Congratulations! You are now setup for ticket splitting!To split a ticket, Decrediton must remain open with your wallet loaded. Establish a partner to split a ticket with in the #ticket_splitting channel on Decred Slack or or here in the Telegram group. Help is available on both platforms with setting up ticket splitting as well.Note: The ticket splitting service will reject any sessions when the ticket price is +/- 5 blocks away from changing. Also, it is strongly recommended that you keep Decrediton open until the ticket purchase transaction changes from pending to confirmed.Need an invite for Slack? Click here!
As I understand it, the vote is given by "lottery". If you contribute 5 DCR you have 5 chances to "win" the vote. If you contribute 50 DRC you get 50 chances.So it's possible for everyone to vote, but more likely the higher contributors will "win".Averaged out over many tickets, even a 5 DCR contributor will eventually get to vote.
Because Pi reads how many tickets you had locked 2 days prior to beginning of vote (this of course launched recently and so was not part of initial ticket splitting) the lottery the ticket-splitter uses is irrelevant. This means there exists currently a potential to "game" the system by being the majority contributor on multiple splits. Due to the extreme low volume of splits (less than 0.1%) this is not a "threat" that is high concern now, however MatheusD already wrote the "hack" version of a solution which could be implemented but requires changes to both the ticket splitter and the Pi system (allowing fractions of votes to be applied to Pi). I think that's a solid solution and for the purpose of budgetary governance superior to lottery in some ways.