Hopefully, disabling signatures is allowed to every member. I agree too, it's not annoying, but I was curious. Signatures tho, are.
You can also disable users signatures on https://bitcointalk.org/index.php?action=profile;sa=themeI don't know if everyone can do that or if it's only for higher ranked users, though. - Don't show users' avatars.
- Don't show users' signatures.
Thank you! Finally got rid of all those ugly spam signatures  |
|
|
|
I think i am moving from IT to agriculture (as i got some land ... ) ,there is no way my IT biz will survive like this ...
What technologies are you working with? IT is very broad and anecdotally IT seems to be one of the sectors that's least affected by the pandemic. Judging by his signature he is in "Web development,Web Design & Graphic Design services". |
|
|
|
<snip> and have to find ways how to acquire more merits and be innovative in doing so.
I thought the whole idea of the merit-system was to get awarded for making quality posts, you make those the merits will follow. If it is about thinking of strategies to acquire more I think it defeats the original purpose. Just my two cents.. |
|
|
|
|
Topic started from a fresh account as first post.
First reply is from another fresh account, created on the same day as OP, as first post endorsing the spammed sited.
Second reply is from another fresh account created one day later.
It's obvious all three account belong to the OP and are used for spamming his site here.
|
|
|
|
So when I create a transaction, i need to sign x times for the x UTXOs in the inputs and increment the index. Am I right?
I am not sure if I'm understanding you question correctly about the inputs and the index. But for the inputs you want to spent you don't have to increment the number. You simply using an unspent output from a previous transaction which has it's own index within the outputs of that transaction. If that didn't make any sense let me try to explain with a (simplified) example: Transaction a1
Index: 0
Output : 1 BTC to your address
Transaction a2
Index: 0
Output : 2 BTC to someone elses address
Index: 1
Output: 3 BTC to someone elses address
Index: 2
Output: 4 BTC to your address
---
So nou you can create a transaction spending 5 BTC (1 from a1 and 4 from a2)
So as input for your transaction you will be using the outputs (including the indexes) from a1 and a2:
Inputs:
a1, index 0 > 1 BTC
a2, index 2 -> 4 BTC
As you can see from my simplified example you didn't have to increase indexes, you need to look them up from previous transaction outputs. |
|
|
|
Well, last week i did make an mainitenance on my old machine and i found one interesting discovery, an very old wallet with some bitcoins.
Very old wallet with transactions from 2019.. your story doesn't make sense. You probably bought a wallet.dat file and got scammed. |
|
|
|
Is there anything original in this research, or is this just a repetition of the original research?
Nah, just another click-bait from Whale Alert showing off stuff done by someone else. Just like the "Did Satoshi just moved coins from an early mined block?" tweet from Whale Alert in May. Anything for the clicks I guess... BTW: If a headline ends in a questionmark you can be sure the answer is NO. |
|
|
|
These addresses have been funded as an experiment on October first 2014: OP_1 -> 33bpsD9CRTsPpx7dW4GtLbZUX7QwFrBvW2
OP_2 -> 3BLfZAdt1syots4kATFfo8sXDk6WZS2YfN
OP_3 -> 31vFvEkyAb2iusbPip36H9rVt6pxExuaVR
OP_4 -> 3CkUmt6tpyj5VhCweGBZpN8bhYnPmSnpD7
OP_5 -> 361xwdrcq4LT7B2zdeJjguycY6S6tqWYZv
OP_6 -> 32f3brEpVCo6y5CnFqpiHDqgsM4LRxT4dX
OP_7 -> 3Mp1a3vgpQST2wA5q9mxTEdeEqNCgUbChF
OP_8 -> 33bpsD9CRTsPpx7dW4GtLbZUX7QwFrBvW2
OP_9 -> 3AHCsW1qsWcNPDwbBKLgtZu9AdRj4YeK7V
In case you wonder why OP_2 to OP_9 work as well since they are not equal to 1 (TRUE) as the final value on stack after all commands are evaluated, well that's because the top element of the stock should be a non-zero value to resolve as valid. But anyway, the article is from 2020 and presented like it's a new thing while this was done already six years ago. |
|
|
|
Anyone know how to modify this code so that it converts the input public key into a compressed P2PKH address instead of uncompressed ?
You don't need to change any code in that function. You pass a compressed public key as parameter to the function and you get the P2PKH-address for the compressed key. Or you pass an uncompressed public key and get the P2PKH-address returned for the uncompressed address. There is no difference between the two in the steps from public key to the base-58 encoded address. #example for uncompressed
pubkey = '041A87E4688D8B9445B5B038CB3B34C186331F1AB4FC0822DCCA44192043EAB3B7ACCF8E941F95AE80B8F373229B7A3F83144160D8982E648F60C8E5CB968EC72E'
print(public_key_to_address(pubkey))
Results in:
Wanting to [041A87E4688D8B9445B5B038CB3B34C186331F1AB4FC0822DCCA44192043EAB3B7ACCF8E941F95AE80B8F373229B7A3F83144160D8982E648F60C8E5CB968EC72E] this to address
1BoatSLRHtKNngkdXEeobR76b53LETtpyT
#example for compressed
pubkey = '021A87E4688D8B9445B5B038CB3B34C186331F1AB4FC0822DCCA44192043EAB3B7'
print(public_key_to_address(pubkey))
Results in:
Wanting to [021A87E4688D8B9445B5B038CB3B34C186331F1AB4FC0822DCCA44192043EAB3B7] this to address
1AYNNMBpXwV7kVveDmFALhCU8VTA3yTs88
|
|
|
|
I know it's less secure, but this way, I am able to discover more addresses.
Ok, well you are of course entitled to ensure your own ideas. My closing words: I would warn everyone strongly against buying such an address: - The private key for the address you buy is not private
- Bitcoin has a rule "your keys, your coins". So in this case: "not your keys, not your coins"
- Why would you want to pay $400+ in BTC equivalent for an unusable address?
|
|
|
|
The address is fully usable. There's just a risk to any vanity address that's generated by a third-party. You trust the third-party to remove the private key. I am not considering myself an attacker and I will permanently destroy the keys.
There is no way of proving you indeed destroyed the key. Bitcoin is trustless, using an address where the private key is known by at least one other party makes it you have to put trust into that party. It is just a really bad idea, disclaimers or not. And there are ways generating vanity addresses by a third-party without the need of exposing the private key to the third party as I've shown. |
|
|
|
|
If you want your idea to use as a public service you should be using the split-key technique which uses a public key provided by the requestor instead.
Taken form the Vanity Search documentation:
Generate a vanity address for a third party using split-key
It is possible to generate a vanity address for a third party in a safe manner using split-key.
For instance, Alice wants a nice prefix but does not have CPU power. Bob has the requested CPU power but cannot know the private key of Alice, Alice has to use a split-key.
Step 1
Alice generates a key pair on her computer then send the generated public key and the wanted prefix to Bob. It can be done by email, nothing is secret. Nevertheless, Alice has to keep safely the private key and not expose it.
VanitySearch.exe -s "AliceSeed" -kp
Priv : L4U2Ca2wyo721n7j9nXM9oUWLzCj19nKtLeJuTXZP3AohW9wVgrH
Pub : 03FC71AE1E88F143E8B05326FC9A83F4DAB93EA88FFEACD37465ED843FCC75AA81
Note: The key pair is a standard SecpK1 key pair and can be generated with a third party software.
Step 2
Bob runs VanitySearch using the Alice's public key and the wanted prefix.
VanitySearch.exe -sp 03FC71AE1E88F143E8B05326FC9A83F4DAB93EA88FFEACD37465ED843FCC75AA81 -gpu -stop -o keyinfo.txt 1ALice
It generates a keyinfo.txt file containing the partial private key.
Pub Addr: 1ALicegohz9YgrLLa4ADCmam7X2Zr6xJZx
PartialPriv: L2hbovuDd8nG4nxjDq1yd5qDsSQiG8xFsAFbHMcThqfjSP6WLg89
Bob sends back this file to Alice. It can also be done by email. The partial private key does not allow anyone to guess the final Alice's private key.
Step 3
Alice can then reconstructs the final private key using her private key (the one generated in step 1) and the keyinfo.txt from Bob.
VanitySearch.exe -rp L4U2Ca2wyo721n7j9nXM9oUWLzCj19nKtLeJuTXZP3AohW9wVgrH keyinfo.txt
Pub Addr: 1ALicegohz9YgrLLa4ADCmam7X2Zr6xJZx
Priv (WIF): p2pkh:L1NHFgT826hYNpNN2qd85S7F7cyZTEJ4QQeEinsCFzknt3nj9gqg
Priv (HEX): 0x7BC226A19A1E9770D3B0584FF2CF89E5D43F0DC19076A7DE1943F284DA3FB2D0
How it works
Basically the -sp (start public key) adds the specified starting public key (let's call it Q) to the starting keys of each threads. That means that when you search (using -sp), you do not search for addr(k.G) but for addr(kpart.G+Q) where k is the private key in the first case and kpart the "partial private key" in the second case. G is the SecpK1 generator point.
Then the requester can reconstruct the final private key by doing kpart+ksecret (mod n) where kpart is the partial private key found by the searcher and ksecret is the private key of Q (Q=ksecret.G). This is the purpose of the -rp option.
The searcher has found a match for addr(kpart.G+ksecret.G) without knowing ksecret so the requester has the wanted address addr(kpart.G+Q) and the corresponding private key kpart+ksecret (mod n). The searcher is not able to guess this final private key because he doesn't know ksecret (he knows only Q).
Note: This explanation is simplified, it does not take care of symmetry and endomorphism optimizations but the idea is the same.
|
|
|
|
Aside from that, these addresses should be used for fun and nobody should permanently keep significant amounts of money on them.
This seems to contradict your earlier statement: "This makes it incredibly hard for attackers to replicate the look of your address". Why would that be important if you are offering an unusable address? |
|
|
|
5 hrs (not yrs!) should not be considered as a cause for concern. Address this site to watch live where your transaction is in the queue of the memory pool. Just a small correction, there is no such thing as "the memory pool" since this can and will differ between full nodes. So the sight you are referring to is the mempool from blockchair's point of view. |
|
|
|
|
Great Business Model: First you sell the private keys to an address and then if the address gets funded you can instantly sweep the funds yourself.
There is really no end to human stupidity but I do hope no one will fall for this kind of scam.
|
|
|
|
One legacy and one segwit. Can it?
Absolutely! Bitcoin uses the Elliptic Curve secp256k1 algorithm to calculate exactly one public key that goes along one private key. However the public key in turn can be used in different ways to make up a human readable format. In short: 1 Private Key -> 1 Public Key -> N addresses
Most used and standard address types: - Legacy, P2PKH based on non-compressed public key
- Legacy, P2PKH based on compressed public key
- P2SH wrapped P2WPKH (Nested Segwit)
- Bech32 Native Segwit
But since addresses can be viewed as a readable form of an input script you could use the same public key to use more exotic and non-standard addresses like: - P2SH-P2PK
- P2SH-P2PKH
- P2SH-1of1MultiSi
- P2SH-(locktime)
- 2WSH(locktime)
- ...
Basically you can come up with an umlimited amount of addresses all based on the same public key which is derived from a single private key. Internally however bitcoin does not use addresses so you should keep in mind every different type from above needs a different unlocking script. |
|
|
|
Craig Steven Wright is a liar and a fraud. He doesn’t have the keys used to sign this message. The Lightning Network is a significant achievement. However, we need to continue work on improving on-chain capacity. Unfortunately, the solution is not to just change a constant in the code or to allow powerful participants to force out others. We are all Satoshi.
You forgot to sign it  But seriously: just copy-paste some stuff and post it as your own will only get you banned. |
|
|
|
How we can recieve a pub key? try to do all without mistakes
i make a from address 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN a pub 3EE4133D991F52FDF6A25C9834E0745AC74248A4 in hash 160, is it right or or everyone use some online stuff for it?
In case of your example you can't find the pubkey of the address 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN. That's because it is a Pay 2 Public Key Hash address. What you tried to do I guess is a base58 decode of the address. The tool at http://gobittest.appspot.com/Address might be of help to you fur understanding purposes. Just fill in the address in the last field and you will get the values all the way to the RIPEMD-160 of the hash of the private key. But since RIPEMD and SHA are hashing algorithms that will only work in one direction there is no way you can calculate the public key. In case of a P2PKH address the public key becomes known when the address is used for an outgoing transaction. In that case for the unlocking script the public key has to be supplied and it will be checked if it hashes to the correct value. But in your case the address doesn't have any outgoing transactions so the public key is not known to anyone but the person who also has the private key. |
|
|
|
Which altcoin uses private key with size of 64, 65 or 70 byte?
None. OP meant a private key for bitcoin with a limited search space for the private key of 64, 65, or 70 bits. Or in other words the bruteforce challange from this topic: https://bitcointalk.org/index.php?topic=1306983.0. |
|
|
|
The 2^115 key was just found, in 11-13 days, using 256 V100s. Now, imagine what you could do with 4,700,000 V100s. (rough numbers using hash power of 1 V100, compared to hashing power that is available for 1 algo on Nicehash)
You can say I don't know the cryptography of BTC and that's fine...but all it would take is to "hack" one private key with a substantial amount of BTC and I believe people would start to sell/move their crypto elsewhere.
You just prove the point we make that you just don't understand this enough. There is a huge difference between a private key made specifically for the purpose of a brute force puzzle/check with a very limited search space and where the public key is known versus a regular private key based upon a random true number. The point is in that last case you could indeed rent 4,700,000 V100s pay for that for the next billion years and still fail. And we are talking about a single address, not all of bitcoin as you claim. |
|
|
|
|
Show Posts
