Search content
Sort by
Showing 20 of 164 results by dudeami
Well, think I did some damage :p
Got it down to -82000, then either the algo changed or it started acting different. All I did was simply choose left/right, then click w/e won the first round twice, then alternate 11 times (this method isn't guaranteed at 15+ bets).
Screenshots:
100%: http://i.gfxtub.com/7897ab.png
92%: http://i.gfxtub.com/7815b1.png
I basically did that a lot, doing 1U bet for the first, then max for the rest, never more than 14 bets, then refresh (sorry if I hit your servers too hard!)
Did I beat it? :p
Got it down to -82000, then either the algo changed or it started acting different. All I did was simply choose left/right, then click w/e won the first round twice, then alternate 11 times (this method isn't guaranteed at 15+ bets).
Screenshots:
100%: http://i.gfxtub.com/7897ab.png
92%: http://i.gfxtub.com/7815b1.png
I basically did that a lot, doing 1U bet for the first, then max for the rest, never more than 14 bets, then refresh (sorry if I hit your servers too hard!)
Did I beat it? :p
Re: Thoughts on the following security features: comodo firewall and keyscrambler
Key scrambler: useless because the attacker can read the key from bitcoin-qt process's memory.
key scrambler is to prevent keyloggers, not the private key. If the attacker gets a hold of the private key of the encrypted wallet, does he still need the passphrase?
No, the private key is what they need. If your wallet is encrypted, your private key is encrypted until you enter a passphrase which then unencrypts the private key into memory for a set amount of time. The private key controls the coins, so obtaining the unencrypted private key is basically the end-game for any hacker. I'd rather see the built in bitcoin-qt encryption refined, so you can control encryption types, similar to truecrypt.
A local bitcoind would be a far better idea. Why introduce an external point of failure you have no control over?
If you can give more details on the site (language?), that would help.
From what I see, your looking for the JSON-RPC API provided with bitcoind (the daemon version of the satoshi client).
Note this will require being able to execute a program in your production environment (aka, not a shared hosting plan) and have enough storage to hold the entire blockchain, as well as a CPU powerful enough to verify the blockchain in a timely manner (this isn't as important). Also note, any bitcoins stored on the site are vulnerable to hacks! Best to send them off to cold storage if they aren't required to be on the site (even then, delayed withdrawl is much better than no withdrawl). Please don't store large amounts of users coins in a hot wallet, I cannot stress this enough! This is the same for a blockchain.info API method where the password/private key is stored on the online machine.
Anyways, the RPC API calls your looking for:
Creating a new wallet
Code:
RPC: 'getnewaddress' 'user-01234'
Returns: '1YourUsersDepositAddress'
Returns: '1YourUsersDepositAddress'
Getting the addresses of an account:
Code:
RPC: 'getaddressesbyaccount' 'user-01234'
Returns: [
'1YourUsersDepositAddress11111',
'1YourUsersDepositAddress22222'
]
Returns: [
'1YourUsersDepositAddress11111',
'1YourUsersDepositAddress22222'
]
Checking the balance of a wallet
Code:
RPC: 'getbalance' 'user-01234'
Returns: 0.00000000
Returns: 0.00000000
Getting transactions (to display non-confirmed transactions)
Code:
RPC: 'listtransactions' 'user-01234'
Returns: {
"account" : "user-01234",
"address" : "1YourUsersDepositAddress",
"category" : "receive",
"amount" : 0.01234567,
"confirmations" : 13172,
"blockhash" : "000000000000002217950f22b11d8c3f6c957b29a764173c7a7562036f2aa17b",
"blockindex" : 93,
"blocktime" : 1378290684,
"txid" : "87fd5e9e...",
"time" : 1378289833,
"timereceived" : 1378289833
}
Returns: {
"account" : "user-01234",
"address" : "1YourUsersDepositAddress",
"category" : "receive",
"amount" : 0.01234567,
"confirmations" : 13172,
"blockhash" : "000000000000002217950f22b11d8c3f6c957b29a764173c7a7562036f2aa17b",
"blockindex" : 93,
"blocktime" : 1378290684,
"txid" : "87fd5e9e...",
"time" : 1378289833,
"timereceived" : 1378289833
}
Send BTC from account/wallet (note this will not go over the users balance)
Code:
RPC: 'sendfrom' 'user-01234' 1WithdrawlAddress 0.01234567
Returns: '87fd5e9e...txid_goes_here'
Returns: '87fd5e9e...txid_goes_here'
Send BTC from server wallet (will take from any account, though account balances will not change):
Code:
RPC: 'sendtoaddress' 1WithdrawlAddress 0.01234567
Returns: '87fd5e9e...txid_goes_here'
Returns: '87fd5e9e...txid_goes_here'
Edit: To clarify, I am piggy backing off of bitcoind's internal account system. This allows multiple addresses to be tied to an account. If you ever want to give your users a new address (or they request it), running the getnewaddress call will give you another address, and both can be used. Note that an accounts balance does not always represent the actual amount of bitcoins in the address tied to the account (due to the ability to move coins off-chain to another account).
If you need more help, feel free to ask!
Hopefully nothing like this :p
http://abcnews.go.com/Technology/dell-latitude-6430u-users-complain-laptop-smells-cat/story?id=20734693
http://abcnews.go.com/Technology/dell-latitude-6430u-users-complain-laptop-smells-cat/story?id=20734693
If you go through the whole blockchain and record every transaction as you plan, you'll probably run into some sort of memory issue. You do have the right approach, though something like this would save you some memory (using JS in a psuedocode kinda way :p):
So basically, you are only storing the transactions that are unspent. Note this approach may be inaccurate due to doublespends and the like.
Code:
var utxos = {}; // Make an object/list
getblock {
foreach block.tx {
getrawtransaction {
foreach tx.vin {
if (utxos[vin.txid+':'+vin.vout])
unset utxos[vin.txid+':'+vin.vout];
}
foreach tx.vout {
utxos[tx.txid+':'+vout.n] = vout; // Note that the vout object does NOT contain the TX ID
}
}
}
}
getblock {
foreach block.tx {
getrawtransaction {
foreach tx.vin {
if (utxos[vin.txid+':'+vin.vout])
unset utxos[vin.txid+':'+vin.vout];
}
foreach tx.vout {
utxos[tx.txid+':'+vout.n] = vout; // Note that the vout object does NOT contain the TX ID
}
}
}
}
So basically, you are only storing the transactions that are unspent. Note this approach may be inaccurate due to doublespends and the like.
Re: Unconfirmed transaction (1BTC bounty paid for resolution!)
The 2nd option. Sorry if my replies are short and blunt. On mobile.
I can't explain what is going on. It doesn't make sense for the wallet to display the transaction as unconfirmed on the transactions tab and not find it when you run getrawtransaction. Either you've somehow accidentally supplied the wrong transactionID, or your wallet is really messed up (corrupted) somehow. Also, I am running Qt on a Mac (like you). I've now tried 3 times, using copy and paste on the displayed transaction ID after double-clicking on the transaction and I can't reproduce the results you got (the -000 on the end of the transaction). I can't seem to figure out how you managed to get transaction IDs that look like that.
You can try deepceleron's instructions to remove the transactions from the Qt wallet, but if it's badly corrupted I'm not sure what the result will be. Make sure you have a backup of the current wallet.dat before you start messing around with pywallet, just in case you make things worse.
At this point, I'd suggest making a backup of wallet.dat and then working with deepceleron and jackjack to clean things up with pywallet.
Good luck. I'll be monitoring this thread and will jump back in if I see an opportunity to help.
Doubt this will help the current situation, but just wanted to let you know how you get the -000. Go to your transactions, right click one of them and select "Copy transaction ID", and you get it in that format with the vout appended.
Hey, have a pure RegExp solution that will work in most circumstances.
This will fail if any unicode characters are used inside of words, but other than that should be selective enough. Example of this failing at the bottom of the post.
Edit: Will also fail when replacing the legit URL's "." with " " (or any other non-alphanumeric, non-unicode character) and having a phishing site for the URL. Expanding the TLD sections to look for real world TLDs could fix this issue to an extent.
Code:
$regex = <<<'REGEXP'
@\[url= # Start of URL BBCode
( # Group 1
((?:https?:\/\/)?) # Group 2, capture protocol if it exists
([\da-z\.-]+) # Group 3, capture the hostname, without the TLD
\. # Need a period between the hostname and TLD
([a-z\.]{2,6}) # Group 4, TLD
((?:[\/\w \.-]*)*\/?) # Group 5, path
)
\]
\s*? # Multiline support
( # Group 6
(?!.*\3.+\4|.*\[img\].*) # Lookahead to check for the non-phishing domain and images
.*?
((?:https?:\/\/)?) # Group 7, phishing URL protocol
( # Group 8, phishing URL host
(?:[\da-z\.-] # Match any characters normally found in a URL
| # or
\[[^\]]+\] # Match any BBCode
| # or
[^\x00-\x7F])+ # Match any unicode characters
)
(?:\.|[^\x00-\x7F]+) # Need a period, but also look for unicode characters
([a-z\.]{2,6}) # TLD
((?:[\/\w \.-]*)*\/?) # Path
.*?
| # or
[^ ]+\[img\].*\[\/img\][^ ]+ # An image with anything other than space spaces surrounding it
)
\s*? # Find any whitespace inbetween
\[/url\] # End of URL BBCode
@xmi
REGEXP;
@\[url= # Start of URL BBCode
( # Group 1
((?:https?:\/\/)?) # Group 2, capture protocol if it exists
([\da-z\.-]+) # Group 3, capture the hostname, without the TLD
\. # Need a period between the hostname and TLD
([a-z\.]{2,6}) # Group 4, TLD
((?:[\/\w \.-]*)*\/?) # Group 5, path
)
\]
\s*? # Multiline support
( # Group 6
(?!.*\3.+\4|.*\[img\].*) # Lookahead to check for the non-phishing domain and images
.*?
((?:https?:\/\/)?) # Group 7, phishing URL protocol
( # Group 8, phishing URL host
(?:[\da-z\.-] # Match any characters normally found in a URL
| # or
\[[^\]]+\] # Match any BBCode
| # or
[^\x00-\x7F])+ # Match any unicode characters
)
(?:\.|[^\x00-\x7F]+) # Need a period, but also look for unicode characters
([a-z\.]{2,6}) # TLD
((?:[\/\w \.-]*)*\/?) # Path
.*?
| # or
[^ ]+\[img\].*\[\/img\][^ ]+ # An image with anything other than space spaces surrounding it
)
\s*? # Find any whitespace inbetween
\[/url\] # End of URL BBCode
@xmi
REGEXP;
This will fail if any unicode characters are used inside of words, but other than that should be selective enough. Example of this failing at the bottom of the post.
Edit: Will also fail when replacing the legit URL's "." with " " (or any other non-alphanumeric, non-unicode character) and having a phishing site for the URL. Expanding the TLD sections to look for real world TLDs could fix this issue to an extent.
| success | Code: [url=http://phishing.com]http://safe-site.com/login.php[/url] | Code: [url=http://phishing.com]http://phishing.com[/url] |
| success | Code: [url=phishing.com] safe-site.com[/url] | Code: [url=phishing.com]phishing.com[/url] |
| success | Code: [url=http://phishing.com]http://safe-site.com/login.php[/url][nobbc]http://safe-site.com/login.php[/url][/nobbc] | Code: [url=http://phishing.com]http://phishing.com[/url][nobbc]http://safe-site.com/login.php[/url][/nobbc] |
| success | Code: [url=http://phishing.com]Welcome to safe-site.com![/url] | Code: [url=http://phishing.com]http://phishing.com[/url] |
| success | Code: [url=http://phishing.com]safe-site.com[/url] | Code: [url=http://phishing.com]http://phishing.com[/url] |
| success | Code: [url=http://phishing.com][b]safe[/b]-site.com[/url] | Code: [url=http://phishing.com]http://phishing.com[/url] |
| success | Code: [url=http://phishing.com]safe-site.io[/url] | Code: [url=http://phishing.com]http://phishing.com[/url] |
| success | Code: [url=http://phishing.com]safe-site⠠com[/url] | Code: [url=http://phishing.com]http://phishing.com[/url] |
| success | Code: [url=http://phishing.com]safe-site .com[/url] | Code: [url=http://phishing.com]http://phishing.com[/url] |
| success | Code: [url=http://phishing.com]s a f e-s i t e.com[/url] | Code: [url=http://phishing.com]http://phishing.com[/url] |
| success | Code: [url=http://safe-site.io]safe-site.com[/url] | Code: [url=http://safe-site.io]http://safe-site.io[/url] |
| success | Code: [url=http://phishing.com]safe-site[img]http://asdf.com/period.png[/img]com[/url] | Code: [url=http://phishing.com]http://phishing.com[/url] |
| failure | Code: [url=http://phishing.com]http://safe-site com[/url] | Code: [url=http://phishing.com]http://safe-site com[/url] |
| success | Code: [url=http://safe-site.com]http://safe-site.com[/url] | Code: [url=http://safe-site.com]http://safe-site.com[/url] |
| success | Code: [url=safe-site.com]safe-site.com[/url] | Code: [url=safe-site.com]safe-site.com[/url] |
| success | Code: [url=http://safe-site.com]safe-site.com[/url] | Code: [url=http://safe-site.com]safe-site.com[/url] |
| success | Code: [url=safe-site.com]http://safe-site.com[/url] | Code: [url=safe-site.com]http://safe-site.com[/url] |
| success | Code: [url=http://safe-site.com][img]http://asdf.com/image.png[/img][/url] | Code: [url=http://safe-site.com][img]http://asdf.com/image.png[/img][/url] |
| success | Code: [url=http://safe-site.com] [img]http://asdf.com/image.png[/img][/url] | Code: [url=http://safe-site.com] [img]http://asdf.com/image.png[/img][/url] |
| success | Code: [url=http://safe-site.com]safe-site.com is a good site[/url] | Code: [url=http://safe-site.com]safe-site.com is a good site[/url] |
| success | Code: [url=http://safe-site.com]Welcome to safe-site.com![/url] | Code: [url=http://safe-site.com]Welcome to safe-site.com![/url] |
| success | Code: [url=http://safe-site.com]こんにちは。[/url] | Code: [url=http://safe-site.com]こんにちは。[/url] |
| success | Code: Some normal text | Code: Some normal text |
| success | Code: [url=http://safe-site.com]☺☺☺ Hello ☺☺☺[/url] | Code: [url=http://safe-site.com]☺☺☺ Hello ☺☺☺[/url] |
| failure | Code: [url=http://safe-site.com]Hello☺World[/url] | Code: [url=http://safe-site.com]http://safe-site.com[/url] |
| success | Code: [url=http://safe-site.com]Hello ☺ World[/url] | Code: [url=http://safe-site.com]Hello ☺ World[/url] |
Re: How to Verify and Validate Bitcoin Transactions of Other Users ??
As Danny said, getrawtransaction and decoderawtransaction is the easiest way to go.
If you checking transactions not related to your wallet, you need to enable the transaction index. Bitcoin uses another method since some version (forget which), due to the tx index being more resource intensive.
To do this, just add:
to your config, shut down bitcoin-qt or bitcoind (if already up), and run
This will take some time, as it has to go through all 10GB of data to make the tx index. In a production environment this can be seen as unacceptable, but easy enough to get around.
If you checking transactions not related to your wallet, you need to enable the transaction index. Bitcoin uses another method since some version (forget which), due to the tx index being more resource intensive.
To do this, just add:
Code:
txindex=1
to your config, shut down bitcoin-qt or bitcoind (if already up), and run
Code:
bitcoind -reindex
This will take some time, as it has to go through all 10GB of data to make the tx index. In a production environment this can be seen as unacceptable, but easy enough to get around.
Is there a reason you can't do that?
Because the old bundles have ended. I've started buying the new ones, but I've missed out on the old ones.
Ahh, maybe specify that in the topic? Sorry for the misunderstanding :p
For what its worth, I did the loan with no questions asked because of their history, as I browsed their past posts and seen a few loans go fine. Also, what they did with the loan doesn't concern me, not everyone getting a loan is desperate and only has that cash.
Though, as I have learned what I say isn't going to mean jack here :p So feel free to think as you please. All I care is that the loan was paid successfully
Though, as I have learned what I say isn't going to mean jack here :p So feel free to think as you please. All I care is that the loan was paid successfully
Vorksholk, bounty has been sent:
http://blockchain.info/tx/ec5b230f460b3ef60b2265084e4d828c4cd0ca392014b0b7d30d0c9e7cea01c6
Thanks again!
http://blockchain.info/tx/ec5b230f460b3ef60b2265084e4d828c4cd0ca392014b0b7d30d0c9e7cea01c6
Thanks again!
Exact same topic: https://bitcointalk.org/index.php?topic=269905.0
Whats been gathered: Either use an escrow or expect no return and the user to run with the coins.
Whats been gathered: Either use an escrow or expect no return and the user to run with the coins.
Re: Exchanging my Btc for your Paypal ( Not going first ) ( No Fee's )
I am selling Btc for paypal
I will not be going first because you can simple chargeback with paypal
Please send me a pm if you are interested
I can show live proof of my wallet
and my btc amount
Current btc stock : 22.76200704 BTC $ 2,412.54
I have no rates
I will not be going first because you can simple chargeback with paypal
Please send me a pm if you are interested
I can show live proof of my wallet
and my btc amount
Current btc stock : 22.76200704 BTC $ 2,412.54
I have no rates
Why not sell using localbitcoins, or the very least an escrow (even if the other party takes the hits on fees). JohnK has pretty good rep around here, so most people would be fine using him.
Also since your a new user that registered today, your trust is non existent. Hopefully no one sends first without a proper escrow
Finally, a picture of a HTML site can be edited very easily. For all we know you have firebug installed and are able to do basic math.