Sollte ja über Bitcoin Core mit sendrawtransaction <hex string> funktionieren nur halt Manual und nicht über ein Skript... Genau. Eine Schleife um den Befehl herum ist dann auch kein Problem mehr. Also mit Liebe verpackt  aber der Befehl im Debug Fenster ist Korrekt? Der Befehl ist korrekt, aber mit cronjob und skript ist es halt einfacher (zu vergessen). |
|
|
|
Ill take a look, thanks.
-snip-
I am too dumb
-snip-
Since we are honest, I dont believe this and I dont think you do. Whatever it will be you are working, Im excited to see what will come out of it.
-snip- (In fact I wrote 'setgenerate true' just for fun and forgot for an hour that the client is running ) I think that one set of binaries is enough for me  It looks like I got ~27% of the networks hash power with 3 cores. Almost no one is mining. Its fun. |
|
|
|
ich wette, dass die Wette auf die Wette nicht kommen wird Wenn ich da jetzt gegenhalt, hab ich dann automatisch gewonnen weil die Wette kam? |
|
|
|
Staking my other signed wallet address for my website:
Address: 1DGEYEkyNb9PqH7jByVQ4QTj8j1gpy5dyS
Message:
Digi-Eye Network wallet address
Signed this 29th of April, 2016
Staked thru Bitcointalk.org
Signature: HA0xec8VRK8AhZXXHLVenf3fmIKZ/U4IweaRE6mRgB4/Y9Cfrb0RzvPHd/1lRjI2j0W+4sM/HeWQUR9ukH3l83I=
Quoted and verified using Bitcoin Core. but verification fails. coinig.com says: "Failure: ('vmB', 'Bad address. Signing: 17AQKneXzx3Hk554sFFxbb8jCFsBydd2XM, received: 1DGEYEkyNb9PqH7jByVQ4QTj8j1gpy5dyS')"
Seems like you created the signature using address 17AQKneXzx3Hk554sFFxbb8jCFsBydd2XM.What am I doing wrong here?You are using coinig, its broken as it cant verify signatures that are on multiple lines. As you said verifies just fine using core. |
|
|
|
I've got a new install electrum watch only wallet with a small balance, an address that I imported from a failed armory installation (armory uses the whole blockchain and that exceeded the drive space on the target machine). When I did the electrum install/import it would only create this wallet as watch only, or maybe I screwed up creating it. I have the armory private keys for the address. I made a second regular wallet in electrum. How do I make a useable wallet out of this mess?
Make sure its a private key you import and not an address. A better option would probably to sweep the balance to a newly created electrum wallet that is covered by a seed though. |
|
|
|
|
~3500[1] BTC, whats it to you?
[1] on segnet
|
|
|
|
it has got three confirmation now :)enjoy
stopped broadcasting |
|
|
|
It just says verifying block on the first loading image.
What can I do about this? I need to transfer some money from a core wallet.
Depending on your CPU/disk this can take a bit. You should see a % value increase. I mean the wallet won't start. It's stuck at this image. img]https://i.imgur.com/WIHC6Yr.png?1[/img] Hmm, what does the debug.log say for the time you started it? How can I see that? Depends on your OS -> https://en.bitcoin.it/wiki/Data_directory#Default_Location |
|
|
|
-snip-
here is the raw for those who want to rebroadcast it
-snip-
rebroadcasting, @OP let me know when its confirmed please. |
|
|
|
It just says verifying block on the first loading image.
What can I do about this? I need to transfer some money from a core wallet.
Depending on your CPU/disk this can take a bit. You should see a % value increase. I mean the wallet won't start. It's stuck at this image.  Hmm, what does the debug.log say for the time you started it? |
|
|
|
Aber keiner der 10% schickt seine "Rechnung.pdf.exe"...
Ist es so schwer, die Dateiendung zu kontrollieren?
-snip-
Guck dir das Video an, großartig erklärt. |
|
|
|
Can anyone explain this in layman's words? Ive looked up other threads but cant work out how the network determines who is rewarded with a block and what calculations your miner is actually doing.
Every time someone who doesnt know about bitcoin asks me about it this is one of the questions that comes up.
Miners search for a hash that seen as a number is lower than the "target". The particular hash function used in bitcoin is sha256d (=sha256(sha256(data)) ). I think its not important to understand the particular hash function, but what hash functions are. A (cryptographic) hash function has a few important properties: - one way; You can not derive the data from the hash itself. - easy to verify; if you have the data you can easily (in terms of CPU cycles) check the hash - collision very unlikely; if you are given a hash its practially impossible to find different data to match the hash If we assume for a second bitcoin would use a hash function that would result in 8 bit values (sha256 procudes 256 bit) and a target of "77" (in decimal) mining could be see like this: target = 0011 1111
hash(0) = 1010 1001
hash(1) = 1010 0101
hash(2) = 0011 1000
The hash values for 0 and 1 are larger than the target so they are discarded. The hash value for 2 is smaller, so we found a block after 3 hashes. Bitcoins current target is 178 659 257 772.5273 higher than the minimum and the entire network is trying ~1.15 billion billion hashes per second to find a block every 10 minutes (on average). "networkhashps": 1.155037292536815e+018,
|
|
|
|
It just says verifying block on the first loading image.
What can I do about this? I need to transfer some money from a core wallet.
Depending on your CPU/disk this can take a bit. You should see a % value increase. |
|
|
|
Just to make sure I understand that right: - users are making bogus escrow attempts with reputable users - only goal of all this is to get their signed message - then, they try to scam someone by sending what they got in the bogus attempt (maybe because they hope that the escrow always uses the same text and only changes the names+date, which could maybe be overseen)  kinda yes, but the message is heavily modified. All sub-steps are removed, there are no user IDs, there is an extra space after Flooores, the BTC amount uses "," instead of "." as a separator and possibly more I missed. I think that is just the lack of attention to detail on the part of the scammer. I would say he probably intended on making it look exactly how you would normally sign an escrow agreement. Probably yes.
Did you ever send a pm to Flooores before he sent you one?
Nope. Isn't the whole point of escrow to bring a 3rd party into the transaction? Why anyone would think they are using escrow because someone sends them a quoted PM is nuts. If you are using user: x as an escrow, be sure you are talking to user x.
Scammers still try this and have so in the past. I know there was one where PMs from OgNasty had been faked. Probably others as well. |
|
|
|
The Tipster Competition signature campaign is back (for one more week). Here is the campaign information once more: [table][tr]
[td][i][color=green]A[/color][/i][/td][td]|[/td]
[td][url=https://bitcointalk.org/index.php?topic=1371799.0]Free Tipster Competition[/url][/td][td]|[/td]
[td]fixed/weekly[/td][td]|[/td]
[td]0.015[/td][td]|[/td]
[td]0.015[/td][td]|[/td]
[td]0.015[/td][td]|[/td]
[td]0.015[/td][td]|[/td]
[td]x[/td][td]|[/td]
[td]x[/td][td]|[/td]
[td]x[/td][td]|[/td]
[td]15/w[/td][td]|[/td]
[td]x[/td][td]|[/td]
[td][b][color=orange]Y/N[/color][/b][/td][td]|[/td]
[/tr][/table]
And the detailed information: Free Tipster Competition ( Thread) Payment period: Weekly Payment method: Will be paid to your Bitcoin address. Minimum posts: 15 posts per week. Maximum posts: - Payments: F/S/H/L: 0.015 BTC per week. Escrow: Yes, No.Miscellaneous: Posts must be made in the Gambling Forum (excluding the Games and rounds, and Investor-based games sub-forums). 8 of the 15 posts must be made in Tipster related threads. A maximum of 4 posts per day will count towards the campaign requirements. Double posts will count as one post only. [b]Free Tipster Competition [/b] ([url=https://bitcointalk.org/index.php?topic=1371799.0]Thread[/url])
[i]Payment period:[/i] Weekly
[i]Payment method:[/i] Will be paid to your Bitcoin address.
[i]Minimum posts:[/i] 15 posts per week.
[i]Maximum posts:[/i] -
[i]Payments:[/i] F/S/H/L: 0.015[BTC] per week.
[u][i]Escrow[/i][/u]: [color=orange]Yes, No.[/color]
[i]Miscellaneous:[/i] Posts must be made in the Gambling Forum (excluding the Games and rounds, and Investor-based games sub-forums). 8 of the 15 posts must be made in Tipster related threads. A maximum of 4 posts per day will count towards the campaign requirements. Double posts will count as one post only.
added -> http://pastebin.com/F9qLQbV1 |
|
|
|
let me know when you downloaded it Got it. Thanks a lot. (Why not to send link to download as a PM? ) idk, didnt think about it. Edit: words |
|
|
|
Just to make sure I understand that right: - users are making bogus escrow attempts with reputable users - only goal of all this is to get their signed message - then, they try to scam someone by sending what they got in the bogus attempt (maybe because they hope that the escrow always uses the same text and only changes the names+date, which could maybe be overseen) kinda yes, but the message is heavily modified. All sub-steps are removed, there are no user IDs, there is an extra space after Flooores, the BTC amount uses "," instead of "." as a separator and possibly more I missed. |
|
|
|
The signature was made by your GPG key on January 6 2016 at 11:26:10 EST, however the signature does not sign the text of the message. Check your outbox and your inbox to find out who you sent a GPG signed message to with that signature around that time.
good idea, found this. -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Escrow by shorena from bitcointalk.org (UID: 181801)
for Gildarts (UID: 532733) as SELLER
and campycoin (UID: 196264) as BUYER
-redacted-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWjUAiAAoJEJQKF9u9a2jizH8QAJLWODpfPrC3wezzm2kNnblv
HhLSZrF4qYHVKKiD46jdBXcXV8Txc7ekw2seOl9pf/A+OwhcZNJIs8tpCIX8d+PF
F4hv1tN2VEzLTrldY8ZCf4x7d85rvJ+DEIyBWeC2EkYR8IsXboqkVTFxdLv08HdO
oBLg1hkMKYU6LcVIedNpD2efZIVM5cmBGvtjr5MZ1SVmoUwxehOyWgaPOcE7LtdP
WNU3mcbChF668AmIZ45xf4njTOcbUyYK8re2l+G8mBM8IV78BlIZbJrwkKYNpPmc
JNAy74bquwJEfL43j80rcfcQ6ERooahntxTmkVLhbSiutASFOrI1p+bCs+jZ4ut1
tm1bwmUKzYRruLFZ3fyFvVxGsBIHWVjtcAmL+WanPul+0rP0tVfBob+0eQtPCeQC
BnGrUqqOyCvfITAcrBF2M0iD174oXsmh1SGQpVw4XYWDn4tC+Tc/1zX1EnLkOVdD
S70MBmtD+BBsZfpYWyw3Ab+uIqdTOSUTp7c7jxzXYo6boml+F9inHo0N8luQN/kH
I8wRSUJhbywlQWvlP5HLqOY6R44euqUu23RaAoJINAk7dK96oE48Rdb+IEL7WfBn
i8ULUVkrkK9Nd4zG1TsuuZHk46hqRHVvPm1YQwt8ZfwA0RP9n5i0ccp9S3/ThLMx
k4cJISkvR9txlI3YV4Xr
=/7Ef
-----END PGP SIGNATURE-----
Deal was never finished. Campycoin didnt send a single PM, it was Gildarts saying they backed out. campycoin stopped posting a day later. |
|
|
|
What happened: The user glovermee tried to use a fake escrow message to trick Flooores. Flooores however is a smart person and did not fall for it, they tried to verify with me and I was able to answer before they send any coins. Scammers Profile Link: https://bitcointalk.org/index.php?action=profile;u=663723Amount Scammed: 0 Payment Method: netteller for btc PM/Chat Logs: !!! WARNING: This user is a newbie. If you are expecting a message from a more veteran member, then this is an imposter !!!
Shorena are you really don't this escrow here for me ? Sorry for this question
"Flooores" You don't have to worry.Just Follow the guideline.
Hi, I was asked to Escrow your deal, I assume the below is what you want. -Sho -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Escrow by shorena from bitcointalk.org (UID: 181801)
for Flooores as SELLER
and glovermee as BUYER
Item: 0,48475124 BTC for neteller payment 240$
Steps:
#0 stay calm, things done properly need time.
#1 Flooores sends escrow the above BTC to 18qw5BLBXv3TS3oKjdhBt2nJvBEZmi99mG
#2 Escrow confirms Flooores to have received the correct amount after 1 confirmation
#3 glovermee issues a USD transfer via netteler to Flooores
#4 Flooores confirms to have received the correct amount
#5 Escrow releases the BTC to glovermee
#6 all are happy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWjUAiAAoJEJQKF9u9a2jizH8QAJLWODpfPrC3wezzm2kNnblv
HhLSZrF4qYHVKKiD46jdBXcXV8Txc7ekw2seOl9pf/A+OwhcZNJIs8tpCIX8d+PF
F4hv1tN2VEzLTrldY8ZCf4x7d85rvJ+DEIyBWeC2EkYR8IsXboqkVTFxdLv08HdO
oBLg1hkMKYU6LcVIedNpD2efZIVM5cmBGvtjr5MZ1SVmoUwxehOyWgaPOcE7LtdP
WNU3mcbChF668AmIZ45xf4njTOcbUyYK8re2l+G8mBM8IV78BlIZbJrwkKYNpPmc
JNAy74bquwJEfL43j80rcfcQ6ERooahntxTmkVLhbSiutASFOrI1p+bCs+jZ4ut1
tm1bwmUKzYRruLFZ3fyFvVxGsBIHWVjtcAmL+WanPul+0rP0tVfBob+0eQtPCeQC
BnGrUqqOyCvfITAcrBF2M0iD174oXsmh1SGQpVw4XYWDn4tC+Tc/1zX1EnLkOVdD
S70MBmtD+BBsZfpYWyw3Ab+uIqdTOSUTp7c7jxzXYo6boml+F9inHo0N8luQN/kH
I8wRSUJhbywlQWvlP5HLqOY6R44euqUu23RaAoJINAk7dK96oE48Rdb+IEL7WfBn
i8ULUVkrkK9Nd4zG1TsuuZHk46hqRHVvPm1YQwt8ZfwA0RP9n5i0ccp9S3/ThLMx
k4cJISkvR9txlI3YV4Xr
=/7Ef
-----END PGP SIGNATURE-----
Additional Notes: I asked Flooores to report the PM to staff so they can be verified. The main reason for this thread is that more people are aware that this is happening. I will always sign escrow agreements. You can verify them here -> https://keybase.io/verify Everything that you can not verify should be considered false.
|
|
|
|
|
Show Posts
