Search content
Sort by
Showing 20 of 128 results by sunsetblues
I keep getting courtesy email notices from empowr.com saying I have an insane balance of 48 million USD in pre-coins.
Anyone else getting those kind of emails?
I can't figure out how they can say my balance is worth that much when it appears you can't even swap pre-coins for USD.
Anyone else getting those kind of emails?
I can't figure out how they can say my balance is worth that much when it appears you can't even swap pre-coins for USD.
Need 3 btc loan for one year I have collateral. Repayment 3 btc +7k USD
I need a 3 BTC loan for one year. I can payback $2,000 USD monthly until paid in full. I have two active websites both established and online for over 15 years I can use as collateral. I can move those domains into escrow while I'm repaying the loan. We can agree on the escrow provider but the domain names must remain pointed at my servers during the loan process so it doesn't interfere with my business operations.
I plan to take the 3 btc and borrow against it at https://nexo.io/ this way if the btc shoots up in value I'm not indebted to the lender for life.
I can provide the lender with my dl, ssn, address, cell phone (I've had the same cell number for 18 years), references, two years financial statements via PayPal, social profile, EIN, tax records. Anything else?
If you're interested in talking with me please send me a PM. If you're a scammer please don't bother wasting your time and my time. I will only deal with someone willing to use an escrow service and prove ownership of their BTC with a signature before I release any private info. This protects me and the lender.
I'm using the funds for operating capital for a new company I've started. I already have a business license for this company, EIN, BOC-3, and registered with the FMCSA, and purchased equipment. Just need a little more capital to get the cash flowing...
I plan to take the 3 btc and borrow against it at https://nexo.io/ this way if the btc shoots up in value I'm not indebted to the lender for life.
I can provide the lender with my dl, ssn, address, cell phone (I've had the same cell number for 18 years), references, two years financial statements via PayPal, social profile, EIN, tax records. Anything else?
If you're interested in talking with me please send me a PM. If you're a scammer please don't bother wasting your time and my time. I will only deal with someone willing to use an escrow service and prove ownership of their BTC with a signature before I release any private info. This protects me and the lender.
I'm using the funds for operating capital for a new company I've started. I already have a business license for this company, EIN, BOC-3, and registered with the FMCSA, and purchased equipment. Just need a little more capital to get the cash flowing...
To sum up, the steps are (I've compressed the whole procedure to a smaller command list):
You should be good this time. Could you check ?
Thanks you!
Code:
$ openssl ecparam -name secp256k1 -genkey -noout -outform DER | \
openssl ec -inform DER -no_public -outform DER -out template.der
read EC key
writing EC key
$ head -c 7 template.der > header.bin
$ echo A114dad00000000000faced00000000000bad000000000decaf00c02bad02bad | xxd -r -p > key.bin
$ tail -c +40 template.der > footer.bin
$ cat header.bin key.bin footer.bin > private_key.der
$ cat private_key.der | openssl asn1parse -in - -inform DER
0:d=0 hl=2 l= 46 cons: SEQUENCE
2:d=1 hl=2 l= 1 prim: INTEGER :01
5:d=1 hl=2 l= 32 prim: OCTET STRING [HEX DUMP]:A114DAD00000000000FACED00000000000BAD000000000DECAF00C02BAD02BAD
39:d=1 hl=2 l= 7 cons: cont [ 0 ]
41:d=2 hl=2 l= 5 prim: OBJECT :secp256k1
$ openssl ec -inform DER -in private_key.der -no_public 2>/dev/null | \
openssl ec -inform PEM -outform DER -out private_key_fixed.der 2>/dev/null
$ openssl ec -check -inform DER -in private_key_fixed.der -noout -text
read EC key
Private-Key: (256 bit)
priv:
a1:14:da:d0:00:00:00:00:00:fa:ce:d0:00:00:00:
00:00:ba:d0:00:00:00:00:de:ca:f0:0c:02:ba:d0:
2b:ad
pub:
04:9f:7d:cb:14:14:21:77:d7:b9:48:78:c4:59:b6:
3a:16:f4:12:80:84:49:b7:8f:a1:7b:e6:4c:d3:7f:
ed:57:a6:42:12:07:e6:ca:95:e0:c5:15:c3:5f:d5:
8c:af:ac:a8:b0:e7:d6:07:a3:3a:2c:5c:b1:6a:de:
28:af:83:15:f7
ASN1 OID: secp256k1
EC Key valid.
$ rm *bin template.der private_key.der
openssl ec -inform DER -no_public -outform DER -out template.der
read EC key
writing EC key
$ head -c 7 template.der > header.bin
$ echo A114dad00000000000faced00000000000bad000000000decaf00c02bad02bad | xxd -r -p > key.bin
$ tail -c +40 template.der > footer.bin
$ cat header.bin key.bin footer.bin > private_key.der
$ cat private_key.der | openssl asn1parse -in - -inform DER
0:d=0 hl=2 l= 46 cons: SEQUENCE
2:d=1 hl=2 l= 1 prim: INTEGER :01
5:d=1 hl=2 l= 32 prim: OCTET STRING [HEX DUMP]:A114DAD00000000000FACED00000000000BAD000000000DECAF00C02BAD02BAD
39:d=1 hl=2 l= 7 cons: cont [ 0 ]
41:d=2 hl=2 l= 5 prim: OBJECT :secp256k1
$ openssl ec -inform DER -in private_key.der -no_public 2>/dev/null | \
openssl ec -inform PEM -outform DER -out private_key_fixed.der 2>/dev/null
$ openssl ec -check -inform DER -in private_key_fixed.der -noout -text
read EC key
Private-Key: (256 bit)
priv:
a1:14:da:d0:00:00:00:00:00:fa:ce:d0:00:00:00:
00:00:ba:d0:00:00:00:00:de:ca:f0:0c:02:ba:d0:
2b:ad
pub:
04:9f:7d:cb:14:14:21:77:d7:b9:48:78:c4:59:b6:
3a:16:f4:12:80:84:49:b7:8f:a1:7b:e6:4c:d3:7f:
ed:57:a6:42:12:07:e6:ca:95:e0:c5:15:c3:5f:d5:
8c:af:ac:a8:b0:e7:d6:07:a3:3a:2c:5c:b1:6a:de:
28:af:83:15:f7
ASN1 OID: secp256k1
EC Key valid.
$ rm *bin template.der private_key.der
You should be good this time. Could you check ?
Thanks you!
That works as expected thank you! I really appreciate you taking the time to send the updated code. If I ever get another spendable merit I'll send it your way. ;0)
A tricky way to do this is to make use of DER files, and to recreate one to import your key. This is a little hacky, but it works.
This is how I did it in a few minutes:
1/ First, create a private key (you won't use, you just need the file structure) in PEM format:
We could directly create a DER file though, using a -outform DER, by the way.
1 (optional)/ What's cool about DER format is that you can dump in ASN.1 its structure. It is interesting and you should take a look at it:
2/ From the private.key PEM file, convert it in DER and extract the header, the key, and the footer.
3/ Replace the key I just created by yours
4/ Rebuild & check the complete DER file
See ? Same structure, different key! Voodoo magic!
5/ recreate your "Key" file:
And we're done.
This is how I did it in a few minutes:
1/ First, create a private key (you won't use, you just need the file structure) in PEM format:
Code:
$ openssl ecparam -name secp256k1 -genkey -noout > private.key
We could directly create a DER file though, using a -outform DER, by the way.
1 (optional)/ What's cool about DER format is that you can dump in ASN.1 its structure. It is interesting and you should take a look at it:
Code:
$ cat private.key | openssl asn1parse -in - -inform DER
0:d=0 hl=2 l= 116 cons: SEQUENCE
2:d=1 hl=2 l= 1 prim: INTEGER :01
5:d=1 hl=2 l= 32 prim: OCTET STRING [HEX DUMP]:BCDA55068C63324BB5CD05696264ED474467A3F1CC95CE83C00BC497F064F4B6
39:d=1 hl=2 l= 7 cons: cont [ 0 ]
41:d=2 hl=2 l= 5 prim: OBJECT :secp256k1
48:d=1 hl=2 l= 68 cons: cont [ 1 ]
50:d=2 hl=2 l= 66 prim: BIT STRING
0:d=0 hl=2 l= 116 cons: SEQUENCE
2:d=1 hl=2 l= 1 prim: INTEGER :01
5:d=1 hl=2 l= 32 prim: OCTET STRING [HEX DUMP]:BCDA55068C63324BB5CD05696264ED474467A3F1CC95CE83C00BC497F064F4B6
39:d=1 hl=2 l= 7 cons: cont [ 0 ]
41:d=2 hl=2 l= 5 prim: OBJECT :secp256k1
48:d=1 hl=2 l= 68 cons: cont [ 1 ]
50:d=2 hl=2 l= 66 prim: BIT STRING
2/ From the private.key PEM file, convert it in DER and extract the header, the key, and the footer.
Code:
$ ll private.key
-rw-------. 1 mycroft mycroft 223 Mar 23 06:51 private.key
$ openssl ec -in private.key -outform DER 2>/dev/null|head -c 7 > header.bin
$ openssl ec -in private.key -outform DER 2>/dev/null|tail -c +8|head -c 32 > key.bin
$ openssl ec -in private.key -outform DER 2>/dev/null|tail -c +40 > footer.bin
$ ll *bin
-rw-rw-r--. 1 mycroft mycroft 79 Mar 23 06:53 footer.bin
-rw-rw-r--. 1 mycroft mycroft 7 Mar 23 06:53 header.bin
-rw-rw-r--. 1 mycroft mycroft 32 Mar 23 06:53 key.bin
-rw-------. 1 mycroft mycroft 223 Mar 23 06:51 private.key
$ openssl ec -in private.key -outform DER 2>/dev/null|head -c 7 > header.bin
$ openssl ec -in private.key -outform DER 2>/dev/null|tail -c +8|head -c 32 > key.bin
$ openssl ec -in private.key -outform DER 2>/dev/null|tail -c +40 > footer.bin
$ ll *bin
-rw-rw-r--. 1 mycroft mycroft 79 Mar 23 06:53 footer.bin
-rw-rw-r--. 1 mycroft mycroft 7 Mar 23 06:53 header.bin
-rw-rw-r--. 1 mycroft mycroft 32 Mar 23 06:53 key.bin
3/ Replace the key I just created by yours
Code:
$ echo A114dad00000000000faced00000000000bad000000000decaf00c02bad02bad | xxd -r -p > key.bin
4/ Rebuild & check the complete DER file
Code:
$ cat header.bin key.bin footer.bin > private_key.der
$ cat private_key.der | openssl asn1parse -in - -inform DER
0:d=0 hl=2 l= 116 cons: SEQUENCE
2:d=1 hl=2 l= 1 prim: INTEGER :01
5:d=1 hl=2 l= 32 prim: OCTET STRING [HEX DUMP]:A114DAD00000000000FACED00000000000BAD000000000DECAF00C02BAD02BAD
39:d=1 hl=2 l= 7 cons: cont [ 0 ]
41:d=2 hl=2 l= 5 prim: OBJECT :secp256k1
48:d=1 hl=2 l= 68 cons: cont [ 1 ]
50:d=2 hl=2 l= 66 prim: BIT STRING
$ cat private_key.der | openssl asn1parse -in - -inform DER
0:d=0 hl=2 l= 116 cons: SEQUENCE
2:d=1 hl=2 l= 1 prim: INTEGER :01
5:d=1 hl=2 l= 32 prim: OCTET STRING [HEX DUMP]:A114DAD00000000000FACED00000000000BAD000000000DECAF00C02BAD02BAD
39:d=1 hl=2 l= 7 cons: cont [ 0 ]
41:d=2 hl=2 l= 5 prim: OBJECT :secp256k1
48:d=1 hl=2 l= 68 cons: cont [ 1 ]
50:d=2 hl=2 l= 66 prim: BIT STRING
See ? Same structure, different key! Voodoo magic!
5/ recreate your "Key" file:
Code:
$ openssl ec -in private_key.der -inform DER -text -noout
read EC key
Private-Key: (256 bit)
priv:
a1:14:da:d0:00:00:00:00:00:fa:ce:d0:00:00:00:
00:00:ba:d0:00:00:00:00:de:ca:f0:0c:02:ba:d0:
2b:ad
pub:
04:d5:53:99:c9:4d:1f:1f:7f:f1:5b:c5:13:d1:96:
34:2b:c8:22:dc:23:9d:f0:55:d6:72:3c:f0:b6:2c:
c8:20:e8:dd:13:40:4b:3a:0d:e5:64:ce:6a:20:e6:
23:ee:2a:17:18:23:d0:6f:0b:13:30:4a:d7:f5:2a:
c2:28:2e:40:33
ASN1 OID: secp256k1
read EC key
Private-Key: (256 bit)
priv:
a1:14:da:d0:00:00:00:00:00:fa:ce:d0:00:00:00:
00:00:ba:d0:00:00:00:00:de:ca:f0:0c:02:ba:d0:
2b:ad
pub:
04:d5:53:99:c9:4d:1f:1f:7f:f1:5b:c5:13:d1:96:
34:2b:c8:22:dc:23:9d:f0:55:d6:72:3c:f0:b6:2c:
c8:20:e8:dd:13:40:4b:3a:0d:e5:64:ce:6a:20:e6:
23:ee:2a:17:18:23:d0:6f:0b:13:30:4a:d7:f5:2a:
c2:28:2e:40:33
ASN1 OID: secp256k1
And we're done.
You're a genius starmyc! Thank you for taking the time to explain this it works like a charm... Sent you the only sendable merit I had. ;0)
Well heck this doesn't work as expected. Run the keccak hash on the public key and the address doesn't match the wallet address for the private key according to myetherwallet.com.
cat Key | grep pub -A 5 | tail -n +2 |tr -d '\n[:space:]:' | sed 's/^04//' > pub
cat pub | keccak-256sum -x -l | tr -d ' -' | tail -c 41 > address
Seems the public key produced belongs to the original key file created when this command was ran:
openssl ecparam -name secp256k1 -genkey -noout > private.key
But I'm still going to call you a genius b/c that hack was pretty clever and taught me some things I didn't know. :0)
A tricky way to do this is to make use of DER files, and to recreate one to import your key. This is a little hacky, but it works.
This is how I did it in a few minutes:
1/ First, create a private key (you won't use, you just need the file structure) in PEM format:
We could directly create a DER file though, using a -outform DER, by the way.
1 (optional)/ What's cool about DER format is that you can dump in ASN.1 its structure. It is interesting and you should take a look at it:
2/ From the private.key PEM file, convert it in DER and extract the header, the key, and the footer.
3/ Replace the key I just created by yours
4/ Rebuild & check the complete DER file
See ? Same structure, different key! Voodoo magic!
5/ recreate your "Key" file:
And we're done.
This is how I did it in a few minutes:
1/ First, create a private key (you won't use, you just need the file structure) in PEM format:
Code:
$ openssl ecparam -name secp256k1 -genkey -noout > private.key
We could directly create a DER file though, using a -outform DER, by the way.
1 (optional)/ What's cool about DER format is that you can dump in ASN.1 its structure. It is interesting and you should take a look at it:
Code:
$ cat private.key | openssl asn1parse -in - -inform DER
0:d=0 hl=2 l= 116 cons: SEQUENCE
2:d=1 hl=2 l= 1 prim: INTEGER :01
5:d=1 hl=2 l= 32 prim: OCTET STRING [HEX DUMP]:BCDA55068C63324BB5CD05696264ED474467A3F1CC95CE83C00BC497F064F4B6
39:d=1 hl=2 l= 7 cons: cont [ 0 ]
41:d=2 hl=2 l= 5 prim: OBJECT :secp256k1
48:d=1 hl=2 l= 68 cons: cont [ 1 ]
50:d=2 hl=2 l= 66 prim: BIT STRING
0:d=0 hl=2 l= 116 cons: SEQUENCE
2:d=1 hl=2 l= 1 prim: INTEGER :01
5:d=1 hl=2 l= 32 prim: OCTET STRING [HEX DUMP]:BCDA55068C63324BB5CD05696264ED474467A3F1CC95CE83C00BC497F064F4B6
39:d=1 hl=2 l= 7 cons: cont [ 0 ]
41:d=2 hl=2 l= 5 prim: OBJECT :secp256k1
48:d=1 hl=2 l= 68 cons: cont [ 1 ]
50:d=2 hl=2 l= 66 prim: BIT STRING
2/ From the private.key PEM file, convert it in DER and extract the header, the key, and the footer.
Code:
$ ll private.key
-rw-------. 1 mycroft mycroft 223 Mar 23 06:51 private.key
$ openssl ec -in private.key -outform DER 2>/dev/null|head -c 7 > header.bin
$ openssl ec -in private.key -outform DER 2>/dev/null|tail -c +8|head -c 32 > key.bin
$ openssl ec -in private.key -outform DER 2>/dev/null|tail -c +40 > footer.bin
$ ll *bin
-rw-rw-r--. 1 mycroft mycroft 79 Mar 23 06:53 footer.bin
-rw-rw-r--. 1 mycroft mycroft 7 Mar 23 06:53 header.bin
-rw-rw-r--. 1 mycroft mycroft 32 Mar 23 06:53 key.bin
-rw-------. 1 mycroft mycroft 223 Mar 23 06:51 private.key
$ openssl ec -in private.key -outform DER 2>/dev/null|head -c 7 > header.bin
$ openssl ec -in private.key -outform DER 2>/dev/null|tail -c +8|head -c 32 > key.bin
$ openssl ec -in private.key -outform DER 2>/dev/null|tail -c +40 > footer.bin
$ ll *bin
-rw-rw-r--. 1 mycroft mycroft 79 Mar 23 06:53 footer.bin
-rw-rw-r--. 1 mycroft mycroft 7 Mar 23 06:53 header.bin
-rw-rw-r--. 1 mycroft mycroft 32 Mar 23 06:53 key.bin
3/ Replace the key I just created by yours
Code:
$ echo A114dad00000000000faced00000000000bad000000000decaf00c02bad02bad | xxd -r -p > key.bin
4/ Rebuild & check the complete DER file
Code:
$ cat header.bin key.bin footer.bin > private_key.der
$ cat private_key.der | openssl asn1parse -in - -inform DER
0:d=0 hl=2 l= 116 cons: SEQUENCE
2:d=1 hl=2 l= 1 prim: INTEGER :01
5:d=1 hl=2 l= 32 prim: OCTET STRING [HEX DUMP]:A114DAD00000000000FACED00000000000BAD000000000DECAF00C02BAD02BAD
39:d=1 hl=2 l= 7 cons: cont [ 0 ]
41:d=2 hl=2 l= 5 prim: OBJECT :secp256k1
48:d=1 hl=2 l= 68 cons: cont [ 1 ]
50:d=2 hl=2 l= 66 prim: BIT STRING
$ cat private_key.der | openssl asn1parse -in - -inform DER
0:d=0 hl=2 l= 116 cons: SEQUENCE
2:d=1 hl=2 l= 1 prim: INTEGER :01
5:d=1 hl=2 l= 32 prim: OCTET STRING [HEX DUMP]:A114DAD00000000000FACED00000000000BAD000000000DECAF00C02BAD02BAD
39:d=1 hl=2 l= 7 cons: cont [ 0 ]
41:d=2 hl=2 l= 5 prim: OBJECT :secp256k1
48:d=1 hl=2 l= 68 cons: cont [ 1 ]
50:d=2 hl=2 l= 66 prim: BIT STRING
See ? Same structure, different key! Voodoo magic!
5/ recreate your "Key" file:
Code:
$ openssl ec -in private_key.der -inform DER -text -noout
read EC key
Private-Key: (256 bit)
priv:
a1:14:da:d0:00:00:00:00:00:fa:ce:d0:00:00:00:
00:00:ba:d0:00:00:00:00:de:ca:f0:0c:02:ba:d0:
2b:ad
pub:
04:d5:53:99:c9:4d:1f:1f:7f:f1:5b:c5:13:d1:96:
34:2b:c8:22:dc:23:9d:f0:55:d6:72:3c:f0:b6:2c:
c8:20:e8:dd:13:40:4b:3a:0d:e5:64:ce:6a:20:e6:
23:ee:2a:17:18:23:d0:6f:0b:13:30:4a:d7:f5:2a:
c2:28:2e:40:33
ASN1 OID: secp256k1
read EC key
Private-Key: (256 bit)
priv:
a1:14:da:d0:00:00:00:00:00:fa:ce:d0:00:00:00:
00:00:ba:d0:00:00:00:00:de:ca:f0:0c:02:ba:d0:
2b:ad
pub:
04:d5:53:99:c9:4d:1f:1f:7f:f1:5b:c5:13:d1:96:
34:2b:c8:22:dc:23:9d:f0:55:d6:72:3c:f0:b6:2c:
c8:20:e8:dd:13:40:4b:3a:0d:e5:64:ce:6a:20:e6:
23:ee:2a:17:18:23:d0:6f:0b:13:30:4a:d7:f5:2a:
c2:28:2e:40:33
ASN1 OID: secp256k1
And we're done.
You're a genius starmyc! Thank you for taking the time to explain this it works like a charm... Sent you the only sendable merit I had. ;0)
I hope someone can help me with this
I'm asking in the bitcoin forum b/c question relates to secp256k1 & openssl.
I understand how to make an ethereum public/private key & public address using linux commands.
From the command prompt three simple steps:
1) openssl ecparam -name secp256k1 -genkey -noout | openssl ec -text -noout > Key
2) cat Key | grep pub -A 5 | tail -n +2 |tr -d '\n[:space:]:' | sed 's/^04//' > pub
3) cat pub | keccak-256sum -x -l | tr -d ' -' | tail -c 41 > address
Wala! All done! Ive got a unique public/private key to use for my ethereum wallet.
But what I cant figure out is how to input a set of numbers/letters into openssl and get the public/private keys like at the end of step 1.
Lets say I like this ethereum private key but I need the public address to use it:
A114dad00000000000faced00000000000bad000000000decaf00c02bad02bad
I know I can go to an online wallet and enter the private key and get the public address which is:
0xB1607e934B61Fc1128AF1E8aa668e33d883aB3b9 (please nobody use this address keys are now public)
but I want to do this from linux prompt and get the answer.
My question: How do I enter that private key into openssl to get the private/public key pair returned something like this result?
Private-Key: (256 bit)
priv:
0b:f3:29:aa:bf:d0:bb:0b:0f:e1:4b:80:54:f2:1a:
2e:38:7d:cd:b5:9b:07:5f:3c:38:99:40:bd:5e:e4:
a4:0f
pub:
04:2f:06:55:11:4a:b1:90:11:00:a4:48:cb:6a:91:
76:f3:01:50:2d:9f:8b:03:ab:cb:8b:67:e7:e7:d0:
3f:85:de:e9:2a:76:59:12:94:4a:4a:ff:94:cd:d7:
97:a2:6b:9c:ae:da:4e:ec:b0:1d:30:c0:55:14:90:
b6:51:dd:75:09
ASN1 OID: secp256k1 (please dont use this key pair its now public)
Thanks in advance for any help Openssl has really got me all messed up trying to figure this out.
I understand how to make an ethereum public/private key & public address using linux commands.
From the command prompt three simple steps:
1) openssl ecparam -name secp256k1 -genkey -noout | openssl ec -text -noout > Key
2) cat Key | grep pub -A 5 | tail -n +2 |tr -d '\n[:space:]:' | sed 's/^04//' > pub
3) cat pub | keccak-256sum -x -l | tr -d ' -' | tail -c 41 > address
Wala! All done! Ive got a unique public/private key to use for my ethereum wallet.
But what I cant figure out is how to input a set of numbers/letters into openssl and get the public/private keys like at the end of step 1.
Lets say I like this ethereum private key but I need the public address to use it:
A114dad00000000000faced00000000000bad000000000decaf00c02bad02bad
I know I can go to an online wallet and enter the private key and get the public address which is:
0xB1607e934B61Fc1128AF1E8aa668e33d883aB3b9 (please nobody use this address keys are now public)
but I want to do this from linux prompt and get the answer.
My question: How do I enter that private key into openssl to get the private/public key pair returned something like this result?
Private-Key: (256 bit)
priv:
0b:f3:29:aa:bf:d0:bb:0b:0f:e1:4b:80:54:f2:1a:
2e:38:7d:cd:b5:9b:07:5f:3c:38:99:40:bd:5e:e4:
a4:0f
pub:
04:2f:06:55:11:4a:b1:90:11:00:a4:48:cb:6a:91:
76:f3:01:50:2d:9f:8b:03:ab:cb:8b:67:e7:e7:d0:
3f:85:de:e9:2a:76:59:12:94:4a:4a:ff:94:cd:d7:
97:a2:6b:9c:ae:da:4e:ec:b0:1d:30:c0:55:14:90:
b6:51:dd:75:09
ASN1 OID: secp256k1 (please dont use this key pair its now public)
Thanks in advance for any help Openssl has really got me all messed up trying to figure this out.
Re: crowdfunding need to raise 45.5 btc for listing on major exchange
Moderator, if you would be kind enough please delete this thread. Other post already deleted... Thank you all for your time.
Moderators don't delete Threads. You should lock it, by using the down-left "Lock" link.
Also deleting your posts for what reason? There is no need to do this... Anyways, good luck to you.
Oh, okay. Was trying to delete so it wouldn't keep getting pulled to the top of the thread, plus posted in the wrong topic so it should be removed.
If by chance someone reading this thread was interested in the project you can keep up with eGo tokens here: https://forkdelta.github.io/#!/trade/eGO-ETH
Thanks for feedback locking topic.
We are tracking CM and offering a reward for Information Leading To Arrest And/Or Conviction Of CoinsMarkets thieves.
A community effort if anyone would like to help...
https://bitcointalk.org/index.php?topic=2185903.msg29953096#msg29953096
CoinsMarkets thugs we will track you down
A community effort if anyone would like to help...
https://bitcointalk.org/index.php?topic=2185903.msg29953096#msg29953096
CoinsMarkets thugs we will track you down
People seems to forget that something like this happened before for example btc-e was down for 3 months after the arrest of some of its people but yet this still return to work under another name and domain,they are wex.nz now.As long as we can see that funds are still on the wallet and are not being moved i will belive that they will comeback
How was they able to track down the btc-e owners? Just wondering if the info will help us in tracking CM owners.
Re: SEGWIT LTC.TBDICE.ORG 0.5% fee SOLO MM LTC/DGE POOL 3K+ LTC/7K+ DGE blks solved
I've been mining for a week at TBdice without any problems. I have pool notifications set to type=51 so I get notices. Of course when I restart my ASIC I get an email notice that says "Worker has been authorized" and this is expected so all is working correctly.
Today without restarting my miner I got two notices that said "Worker has been authorized" for worker 1 & 2, but I hadn't restarted my miner it was running just fine. It happened at the exact time when Pool Block 1361150 hit (think that's the correct number). What makes this really weird is the two emails I received included two additional email addresses I've never seen before. You can find my workers with Lbwrx.
Bug maybe?
Today without restarting my miner I got two notices that said "Worker has been authorized" for worker 1 & 2, but I hadn't restarted my miner it was running just fine. It happened at the exact time when Pool Block 1361150 hit (think that's the correct number). What makes this really weird is the two emails I received included two additional email addresses I've never seen before. You can find my workers with Lbwrx.
Bug maybe?
Hi,
This seems odd. Can you PM me mail message headers to investigate this case further?
10X
Best
Loshia
PS: Some logs and all seems good
[2018-02-02 01:55:07.956] Authorised client 4821322 Lbwrx......
[2018-02-02 01:55:07.966] Authorised client 4821321 Lbwrx......
[2018-02-02 22:19:25.386] Authorised client 4834871 Lbwrx......
[2018-02-02 22:51:28.929] Authorised client 4835425 Lbwrx......
And two mails sent around
/var/log/exim4/mainlog.1:2018-02-02 01:56:04 1ehOi1-0003HS-TO => teaxxxxxrt@goxxxxs.org R=dnslookup T=remote_smtp H=smtp.gxxxxs.org [xxx.xxx.xxx.xxx] X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128 DN="C=US.....
/var/log/exim4/mainlog.1:2018-02-02 01:56:04 1ehOi2-0003HW-04 => teaxxxxxrt@goxxxxs.org R=dnslookup T=remote_smtp H=smtp.gxxxxs.org [xxx.xxx.xxx.xxx] X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128 DN="C=US.....
/var/log/exim4/mainlog:2018-02-02 22:21:05 1ehhpW-00047i-RM =>teaxxxxxrt@goxxxxs.org R=dnslookup T=remote_smtp H=smtp.gxxxxs.org [xxx.xxx.xxx.xxx] X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128 DN="C=US.....
/var/log/exim4/mainlog:2018-02-02 22:53:04 1ehiKV-0004Nx-0X =>teaxxxxxrt@goxxxxs.org R=dnslookup T=remote_smtp H=smtp.gxxxxs.org [xxx.xxx.xxx.xxx] X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128 DN="C=US.....
PM sent.
Re: SEGWIT LTC.TBDICE.ORG 0.5% fee SOLO MM LTC/DGE POOL 3K+ LTC/7K+ DGE blks solved
I've been mining for a week at TBdice without any problems. I have pool notifications set to type=51 so I get notices. Of course when I restart my ASIC I get an email notice that says "Worker has been authorized" and this is expected so all is working correctly.
Today without restarting my miner I got two notices that said "Worker has been authorized" for worker 1 & 2, but I hadn't restarted my miner it was running just fine. It happened at the exact time when Pool Block 1361150 hit (think that's the correct number). What makes this really weird is the two emails I received included two additional email addresses I've never seen before. You can find my workers with Lbwrx.
Bug maybe?
Today without restarting my miner I got two notices that said "Worker has been authorized" for worker 1 & 2, but I hadn't restarted my miner it was running just fine. It happened at the exact time when Pool Block 1361150 hit (think that's the correct number). What makes this really weird is the two emails I received included two additional email addresses I've never seen before. You can find my workers with Lbwrx.
Bug maybe?
⭐ Merited by grendel25 (1)
So many of you here should not be investing in crypto with your money. Embarrassing.
lol, so true. Ice cold liquid titanium flows through the veins of us serious crypto traders! Well... maybe Mt Dew, Code Red, coffee... etc.
Really though, glad to see the new update from CM. Personally, I think they do owe us a daily update to that "news" link. It is the least they could do. Even if it's just an update saying nothing new but just a reassurance that there is someone on the other end.
They do own a lot of responsibility for how bad this has turned out. I don't doubt many people were physically ill from all the stress out of this.
I'm okay. I'm patient. Not freaking out and calling this a scam... not yet anyways. Then again, I don't have as much on the line as some people here. But I do have enough in CM to make me very interested in how this turns out. Besides that, I really liked the platform and how they support staking through wallets on their site. I truly hope they come back stronger than ever.
I said the same thing about NiceHash when they got hacked a few weeks ago. I'm proud of NH for recovering and I hope to be proud of CM on their recovery.
Let's go.
If I had a merit to give out you certainly would have got one with that post. Guess a +1 will have to do...
Still kinda think were dealing with kids though just cause the way its been handled... I'm calling it a night, but I thought it'd be nice to share a merit joke with everyone before leaving, just to make some of you smile. 
.
A man appears before St. Peter at the pearly gates. 'Have you ever done anything of particular merit?' St. Peter asks.
Well, I can think of one thing, the man offers. Once, on a trip to the Black Hills, out in South Dakota, I came upon a gang of high-testosterone bikers who were threatening a young woman. I directed them to leave her alone, but they wouldn't listen. So I approached the largest and most heavily tattooed biker. I smacked him on the head, kicked his bike over, ripped out his nose ring and threw it on the ground, and told him, Leave her alone now or you'll answer to me.
St. Peter was impressed. When did this happen?
Just a couple of minutes ago.
.A man appears before St. Peter at the pearly gates. 'Have you ever done anything of particular merit?' St. Peter asks.
Well, I can think of one thing, the man offers. Once, on a trip to the Black Hills, out in South Dakota, I came upon a gang of high-testosterone bikers who were threatening a young woman. I directed them to leave her alone, but they wouldn't listen. So I approached the largest and most heavily tattooed biker. I smacked him on the head, kicked his bike over, ripped out his nose ring and threw it on the ground, and told him, Leave her alone now or you'll answer to me.
St. Peter was impressed. When did this happen?
Just a couple of minutes ago.