 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
I've reached an agreement with Leo Medina to sell bustabit and bustadice. While most of you know him as the operator of MoneyPot, he's worked with me as part of our developer team behind the scenes for several years.
Here's what's happening:
Next Monday (February 26) at 15:00 UTC bustabit will go offline during its regular maintenance window and Leo will step in to take over. Because of the complicated nature of the transfer we expect the downtime to last longer than usual, up to a few hours. We will keep this thread updated with our progress.
What happens to bankroll investments?
I have reached out to all bankroll investors via email and asked those that do not want to remain invested in the bankroll to divest. Investors that I haven't been able to get in touch with by next week will be divested prior to the handover. It goes without saying that all users including investors are free to withdraw all their money at any time.
Hey Daniel, Thanks for running the site the way you did! Do you have a new project in mind or just plan to chill? Also, double check if all emails to investors were correctly sent out, some accounts might have not got it. (Can DM me for more info) |
|
|
|
For those who do not believe the keys are random: what would be the next value?  < 2.5 |
|
|
|
DO NOT CLICK ON THE LINK FROM SILKYSTARR!!!! The link takes you to a website which is chipmixeŗ.com and not the original. The r is a special character and this will be a fraud site. Please always type in the URL and don't just click on links from users. edit: it looks like the Bitcoin Address: 1LysC2YArFGSyN7ZT77RKQuTtg54icpREH is always the same and people have deposited into it. Maybe I'm lucky man, but clearnet link work for me [URL REMOVED FOR SAFETY])  But Tor link doesn't working (captcha...) I hope the Tor site will work soon  Dangerous because it seem's to pass chrome's IDN policy and displays unicode instead of punycode. Firefox has a user flag for those that wish to force enable punycode, chrome doesn't. https://www.chromium.org/developers/design-documents/idn-in-google-chrome |
|
|
|
|
Is the investigation pending forever? Fairlay should provide an estimated of when they will complete the "investigation". This should be communicated privately to the player or with the player's permission.... publicly to the community. A statement should be made by them so they can be judged by the community on their decision, otherwise as of right now, without ANY information communicated publicly OR privately, this is stealing/scam.(communicating just to 3rd party such as SBR doesn't count unless their is good reason for it, and it seems as SBR is on the players side at the moment)
Also, if Fairlay did in fact make a mistake or was negligence in handling the matter appropriately, when returning the funds they should provide additional compensation for the fund freeze, because of the extended time and lack of transparency and communication regarding the matter. The compensation should be excessive, such as equal to the amount frozen, if they want to make good with the player and community.
|
|
|
|
|
Fairlay should not only return the frozen funds, but also provide compensation if it was done in their error:
-failure to communicate to customer while communicating information to other channels
-said they will give a phone call, but didn't
-have arbitration listed in TOS, but don't actual provide it
-didn't provide any information to the cause and nature of the incident, nor a timeline for resolution
They will need a very solid explanation for the lack of transparency in their actions. Most services and exchanges return funds for violation of TOS, and just ban the account. Even then, unless an exchanged is defrauded (via hack or other means), freezing money indefinitely and keeping it is stealing. It would only be acceptable to transfer it to the damaged party or the legal system jurisdiction overseeing the manner.
|
|
|
|
|
Where does PrimeDice draw the line on advertising the theoretically possible, but close to impossible, 112 BTC Jackpot?
1) Would PriceDice feel its ethical for a site to advertise a 11,200 btc jackpot, with similar rules:
Roll 77.77 twice in a row to win! The percentage of the jackpot won depends on how much you bet.
Over 1 BTC: 100%
Over 0.1 BTC 10%
Over 0.01 BTC 1%
Over 0.001 BTC 0.1%
Over 0.0001 BTC 0.01%
Yes its theoretically possible to win, but requires betting 1 BTC one hundred million times to have a good chance of winning it, and in the process you will lose around 1 million BTC to the house edge.
2)This is very borderline false advertising, using such a high amount jackpot in a title of your post without details
Example of a similar unethical title for comparison: Free 112 BTC deposit bonus
Fine Print Rules: Earn up to a matching 112 btc bonus, must wager 10000 times deposit to earn the bonus
3) Basically you are unethical luring players via a jackpot that will no one will ever win.
|
|
|
|
|
I can't believe everyone got this wrong:
There is only one way certain way to prove ownership, and that is by giving your PRIVATE KEY to that someone.
After that moment, both you and them become "owners" of that address as both of you control the ability to sign messages and move funds (if any exist). If one of you discards the private key, and has no physical/mental backup of it, nor any recollection, they lose ownership.
1) Having a signed message that belongs to that public hash does NOT prove you have ownership, it's mearly proves to someone, that you possess that signed message, but you might or might not be the orginal actual signer or owner.
2) Showing that a dust amount from that address has been sent to another address of someone's choice, does NOT prove you have ownership, it only proves that someone, but not nessesary you, is the owner.
A good real life example of the misconceptions of 1 or 2 is all the OTC scams that take place, where the scammer is a man in the middle but appears to be an owner.
If you want to prove ownership of an address that has funds, you move the funds out first, and give out the private key, proving that at one point you possessed ownership of the previous address that had a balance. (Warning: giving out a single private key and xpub key for an unhardened hd wallet derivation can lead to an attacker taking all your wallet funds)
|
|
|
|
I withdrew a very small amount and got a pop up saying something about how it would have to be done manually
It's going on 7+ hours.
Any known issues with payouts?
It ranges from a few hours, to a few days. And sometimes you need to email them to remind them. Eventually you will get it. - Instant withdrawals and deposits -- Send Bitcoins to the address provided and start playing right away! Withdrawals are just as fast.
They advertise this, which is not true in all cases, its true for small withdrawals and when the hot wallet is not empty. |
|
|
|
...
2. At the time of writing his investment would represent
a share of ~15 % of the total bankroll (1000 BTC / 5539 BTC (currently invested) + 1000 BTC (his investment)).
...
Actually these numbers would be slightly worse, because the 20 BTC dilution fee would be part of the total bankroll as well. I should have used the following calculation: 980 / 5539 + 20 + 980 = ~0.148 % It's my understanding that the dilution fee is applied right after NOT right before the investment, therefore a new investor will get part of his own dilution fee back, which is important for a large investor. Example: whole site bankroll is 1 btc, and you invest 100 btc, you will get around 1.99 of the 2btc dilution fee back right away. Good luck with the girl. |
|
|
|
|
In addition to the IP, to prevent abuse just have more captchas. Solve one captcha for the first claim, two for the second claim...five for the fifth claim.
An alternative, you can present the user with 10 captchas, 5 of which are real and 5 are which are from a "solve a captchas" bitcoin paying service.
5 captchas solved are worth about 3 bits and should provide a nice way for users to fund the faucet for you.
|
|
|
|
The 50th million spin was a day ago. |
|
|
|
It seems to me that a better way of doing it would be to say "do you want this medium priority or high priority" and showing the average fees each option takes, and then deducting the exact amount of the fees you pay (as directed by the customer) from the withdraw.
Yeah, I see. It's the wording you're objecting to. JD says "0.001 CLAM will be deducted from the amount you type for use as a transaction fee" which also isn't strictly true. It will be used as a transaction fee, but not necessarily for *your* transaction. Agree with Dooglus, just fix the wording from: "MoneyPot uses a fixed transaction fee that is specified by the user in the calculation of the actual transaction fee." to "MoneyPot uses the priority level that is specified by the user, and will be charge a fixed fee for the transaction. Actual fee used in the transaction is dynamic and can vary based on transaction size and bitcoin network transaction activity" And in the selection, "Default - 200 bits (per kb) Priority - 300 bits (per kb)" to "Default - Fee: 200 bits Priority - Fee: 300 bits " Problem solved. |
|
|
|
Using create-unsigned-tx.py I get a "TypeError: Non-hexadecimal digit found" after I input the corresponding private key for the auth UTXO. Traceback (most recent call last):
File "create-unsigned-tx.py", line 300, in <module>
main()
File "create-unsigned-tx.py", line 262, in main
magicbyte=get_p2pk_vbyte()):
File "/home/mint/Desktop/joinmarket-0.1.4/bitcoin/secp256k1_main.py", line 18, in privkey_to_address
return pubkey_to_address(privkey_to_pubkey(priv, from_hex), magicbyte)
File "/home/mint/Desktop/joinmarket-0.1.4/bitcoin/secp256k1_main.py", line 269, in privkey_to_pubkey
return privkey_to_pubkey_inner(priv, usehex)
File "/home/mint/Desktop/joinmarket-0.1.4/bitcoin/secp256k1_main.py", line 228, in func_wrapper
newargs += [arg.decode('hex')]
File "/usr/lib/python2.7/encodings/hex_codec.py", line 42, in hex_decode
output = binascii.a2b_hex(input)
TypeError: Non-hexadecimal digit found Also tried using the testnet example from the github wiki and got the same error. |
|
|
|
Sorry @VTC!
This is a bit unclear for me, can you offer an example?
Say a user deposits 10 btc. They can create 10 unmatched bets of 10 btc each for a total of 100btc in market liquidity, right?
right.
Are you saying that after the first 10 btc gets matched, the other 90 btc won't get canceled?
yes.
And if another user tries to bet against those remaining 90btc will the system allow a match putting the original user into a negative balance plus 0.1mBTC fee?
no, the system won't allow a match. The offer will be cancelled and the penalty deducted from the account. With the 90 btc in the given example not being auto canceled, won't this effect other users who see these bets as on the books as providing liquidity, yet they can't bet against it? What is the purpose of the penalty, is it to deter users from providing liquidity, or to fund supports time as a manual review/operation has to be done? Technically users can set up a 24/7 system to self monitor and cancel bets over there balance via api, but that is much more work then fairlay doing it on their side by default (with perhaps an option to opt out, for liquidity providers who plan to add more balance and don't want bets canceled) Your system is able to monitor and impose a penalty (and I'm assuming avoid any race condition bugs/exploits) yet it can't be set up to auto cancel these bets instead? |
|
|
|
In the upcoming weeks we will migrate all accounts to an enhanced and more secure system. Affected users will get a new deposit address and be notified via email. New Features: - All users who like to trade their position are now able to pull out their money early.
- Unmatched bets will no longer result in a reduction of your balance. This way everyone can be market maker on many markets without being forced to deposit too much money.
- Instead, the funds will be deducted from your balance right before a bet is matched.
- All market makers are required to make sure that they can cover for their unmatched bets. If a market maker fails do so (one of his unmatched orders is about to get matched and he does not have the necessary funds), it will result in a penalty of 0.1mBTC in each case.
This is a bit unclear for me, can you offer an example? Say a user deposits 10 btc. They can create 10 unmatched bets of 10 btc each for a total of 100btc in market liquidity, right? Are you saying that after the first 10 btc gets matched, the other 90 btc won't get canceled? And if another user tries to bet against those remaining 90btc will the system allow a match putting the original user into a negative balance plus 0.1mBTC fee? |
|
|
|
|
I said lower the discount not increase it :-)
If you are almost sold out that means you shouldn't be selling them so cheap.
|
|
|
|
|
Looks like so far no one has had issues with your giftcards, so if they are in fact more or less legit, you should consider lowering the discount, pretty sure you will still sell out.
|
|
|
|
From now on, users will no longer be able to pick their own password. The site is going to generate you something nice and secure, which you can write down. No matter how much I tried, users kept reusing passwords and it was a never-ending war trying to prevent accounts being hacked (there's sites like leakedsource which have millions of peoples reused passwords). Old passwords are still valid, although I'd encourage everyone who didn't use a password manager to randomly generate one to change it. I apologize in advance about the inconvenience, and if you're prone to losing your password please make sure to set a recovery email.  It's generated client side so more advanced users can still pick their own :-) I suggest you make the client side generator 4 English words from this wordlist: https://github.com/bitcoin/bips/blob/master/bip-0039/english.txtIt will be a similar amount of entropy as your generator (~44bits along with reCAPTCHA) but much easier to remember and write down. http://preshing.com/20110811/xkcd-password-generator/Edit: You can even get by on just 3 words (33bits) since this will be 8.5 billion combinations. Cost to solve 1000 google reCAPTCHAs ~ $0.80 cents. And no one has $6 million USD in their bustabit account to be targeted. |
|
|
|
|
