--snip--
My TOR when the opening site is bit slow, it's different when I use yomix on clearnet browser. but so far all going smoothly. 1 hour after mixering, I received mixed btc same as calculate from the legacy address. Of course using .onion link (on Tor Browser) is slower than accessing regular website on regular browser. After all Tor use at 3 hop to access any website and optional additional 3 hop when you access .onion link. So what kind of mixing yomix method use?, Are they use coinjoin or whirlpool?.
Probably their own mixing method/algorithm. And FYI, whirlpool is a type of CoinJoin. |
|
|
|
Fortunately most Bitcoin wallet these days doesn't have ability to generate P2PK address.
Does this mean P2SH and bech32 are considered safer ? I only thought they were faster but security-wise all types depend on only one blockchain. Other types of Bitcoin address are deemed safer since, 1. It's public key isn't revealed until you spend the coin. 2. QC takes some time to find private key from elevated public key. And talking about security on P2SH, it gets more complex due to custom script (e.g. P2SH for 2-of-3 multisignature) and 80-bit security size. |
|
|
|
Transaction ID: Pending Reflection ID
Status: Pending
Definitely fake, there's no thing such as "Pending Reflection ID". It should show text "Unknown" instead for unsigned transaction and TXID for signed transaction. |
|
|
|
Never happened to me, although when i use CEX i prefer local exchange which might be less strict compared with international ones. Some people may abuse this system by creating multiple accounts and posting spam in order to earn more Bitcoin, which can negatively affect the reputation of the project or service being advertised. As a result, exchanges may block transactions from these earnings as a precautionary measure to prevent potential fraud or scams.
Is there any documented case about this? I have doubt any exchange care the funds comes from service which spam this forum. 3. Technical issues: Transactions may be blocked if the exchange is experiencing technical difficulties or if there is a problem with the transaction itself.
There shouldn't be any problem the transaction itself since in general Bitcoin transaction is either, 1. Invalid transaction, which cannot be broadcasted to node/miner. 2. Valid transaction, with specific amount of confirmation. |
|
|
|
|
After reading whole accusation and @Mitch212 trust feedback, i thought something interesting. Rather than buying merit (AFAIK starts from $5/merit), merit fishing on Wall Observer or doing certain task (such as sign with PGP/bicoin address), merit/account farmer could choose host small giveaway instead. For example, if @Mitch212 were to deliverer his promise, he could got a good deal ($25/20 merit or $1.25/merit). And the cost could be reduced to almost $0 if he decide to make his altcoin as winner.
And i also agree there's no sufficient proof about connection between @Rbah and @Mitch212. I decide to join his giveaway and see whether he'll deliver his promise or not.
|
|
|
|
Lately I've been wondering if we can find out who ignored us. Is there any way to find out who ignored us?  There's no way to tell who's ignoring you on bitcointalk forum since the feature to block or ignore people isn't out in the open. If you think someone's giving you the cold shoulder, the best bet is to message them directly and ask. IMO it's not good advice when the receiver could report your PM with reason "unsolicited/unwanted PM". If you ask to multiple users at once and some of them decide to report your PM, you might get temporary ban. |
|
|
|
My understanding is that you can get rid of addresses and have people sign utxo's directly with ECC.
And having people share script (which contain condition to spend/lock the Bitcoin) instead? It seems that addresses sorta function like accounts in eth and utxos's function for transactions in mimble wimble. Bitcoin seems to have both utxos and addresses and has some of the downsides of both approaches.
Wrong, bitcoin address basically is just abstraction/representative of script. It's also the reason you could send and receive Bitcoin using same address. |
|
|
|
2nd, how to use Brute-Force to recover the password?
If you decide to use software "btcrecover", the author also provide video tutorial on youtube ( https://www.youtube.com/playlist?list=PL7rfJxwogDzmd1IanPrmlTg3ewAIq-BZJ) which should give you an idea how to use this tool. 4th, If we know the length of the password, for example, 12 characters, how we could start, and where we could finish? how long it takes with a good GPU?
It also depends on which character do you use, which affect total possible password combination. Here's an calculation example with following detail, Total unique character used = 26 (lower case) + 10 (number) = 32 character. Total possible password combination = 32 character ^ 8 character length = 1099511627776 (about 1.09E12). Speed of RTX 2080 Ti = 6.4 kP/s or 6400 password per seconds. 1 day in seconds = 60 * 60 * 24 = 86400 seconds. Brute force time (in days) = 1.09E12 / 6400 / 86400 = ~1971 days. |
|
|
|
which is also stated in this article[1]
[1] coingeek[dot]com/fork-ahead-bitcoin-cash-will-fork-bigger-blocks-august-1/
That website basically is BSV propaganda, please don't use it as reference. Who knows what kind of false information they intentionally include. This article doesn't touch problem of block size in detail. https://en.bitcoin.it/wiki/Block_size_limit_controversy should be good addition of Aaron's article. |
|
|
|
- no need to advertise new address each time to receive transfer,
This is fair point, especially for small organization/individual who accept Bitcoin as donation option. - less risk of mistake on sender side,
I get your point. But the sender could just re-check latest Bitcoin address mentioned by receiver. Lastly, protection is simpler for one private key than many of them (even if they are generated in a deterministic way like BIP-32 or BIP-39).
Mostly irrelevant due to HD wallet where user only need to backup recovery phrase/words or master private key (also called xprv). And on practice, they need to protect their device and wallet file instead. |
|
|
|
You can also try the following: - You can use local database instead of Redis to store the transaction ID since local database is faster in terms of read/write speed, which can help to filter duplicates.
--snip-- CMIIW, but doesn't Redis has faster performance/response time compared to local database since Redis store the data/index on RAM? - Increase the minimum transaction fee required for a transaction to be considered valid. This can help prevent spam transactions, which may be causing the duplicate notifications.
It can be done by changing value of minrelaytxfee parameter, but OP's system will not see incoming transaction until it's included on the block. It has some trade-off if OP running a service where the customer want to know the system already detect their transaction. - You can als use a different type of notification system that is less prone to duplicates, such as the -walletnotify command, which allows you to specify a command to be executed when a new transaction is detected.
Did you mistype something? OP already use walletnotify. The only other relevant notification option on Bitcoin Core is blocknotify. - You can also look into the transaction confirmation time, if the confirmation time is low then it increases the chances of duplicate transaction. So you can increase the confirmation time for the transaction to make sure you are notified after the transaction is confirmed.
This doesn't make sesnse since walletnotify make notification when the transaction is on mempool (has 0 block confirmation) and included on block (has 1 block confirmation). And time when node receive the transaction or timestamp on block isn't very reliable. |
|
|
|
if you have 2 different receiving addresses on the core wallet, can you send satoshis 'internally' from one to the other addy?
Yes, you can do that. I just tried on testnet version. is there anything in particular that needs to be taken into account?
Can't think anything since Bitcoin Core already makes it clear by specific "Payment to yourself" if you check the transaction on "Transaction" tab. |
|
|
|
The first 4 posts were deleted quickly after I reported them, but I feel like it's not enough. Considering the recent hype on text-spinning AIs, and considering how easy it is for shitposters to produce massive numbers of posts that take some time to read through to realize it's bogus, I'd like to see them banned quicker. Maybe we can still stop this before it reaches massive volumes.
I agree with @suchmoon, so it's more realistic to either 1. Keep reporting those posts. At bare minimum, they'll focus spamming on different board. 2. Quote their reply with detailed explanation why their post either doesn't make sense or could be dangerous towards other user. 3. Ignore them. I wonder how difficult it really would be to add a captcha requirement for every post.
It'll be nightmare towards VPN and Tor user who already face occasional CloudFlare "security check". And it's publicly known popular CAPTCHA service (such as hCaptcha and reCATCHA) is hostile towards VPN and Tor. |
|
|
|
My question is, is there a way to help recover his wallet?
Assuming either the password is either short or your friend remember parts of the password, brute-force is possible within reasonable time. It comes down whether you choose to, 1. Use your own computer. Least amount of trust is required, but you usually either need to be patient (if you have slow computer) or make big initial investment (if you're willing to buy high end GPU). 2. Use cloud computing service such as vast.ai. Some trust is required, but usually is cheaper for short term usage. 3. Ask for help reputable from service. Few member mention https://www.walletrecoveryservices.com/, but i never try to use this service. |
|
|
|
So my private key is 66 characters long, but when i conver it to 130 characters it no longer validate my adress, but the 66 one do?
Are you trying to say you tried to generate uncompressed public key (which has 130 character) or public key (which has 66 character) based on your private key? A couple of things don't make sense in your post. So my private key is 66 characters long,
What kind of encoding does it use? WIF (Base58) produces 51-52 characters, Hex (Base16) produces 64 characters and Base64 produces less (44 characters). HEX private key with 2 character padding which indicate compressed/uncompressed also exist, see Compressed hex private key with 66 characters?. It's also possible certain software decide to add prefix 0x to indicate the format is hex. |
|
|
|
So I thought it would be better not to rely on one source. Considering that I haven't written SecureRandom library myself and that I am unable to find details on how it works and how it generates entropy, I decided to add two more entropy sources. One that is "decided" by the user and one that is "decided" by time.
Thanks for the explanation. While i understand rationale behind the decision, there are few things i'd like to comment. 1. I have doubt using time improve the security since the attacker (assuming they know how the private key is generated) could reduce search space between time you create this library and first time the address receive Bitcoin. 2. I'm not sure how useful is 52-bit entropy from 2 different source when anything less than 112-bit no longer recommended these days. 3. Some details of Java's SecureRandom can be seen at https://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html#SecureRandomImp. |
|
|
|
--snip--
I don't know if this can help you dude, but try to go on udrop.com where you can bitcoins private keys finder Here is the link: [LINK SNIPPED] or it could be that your private key has made an error, you may have just one letter missing from your private key or replaced by another letter. Have you tried this tool personally? I did quick check and i'm 99.99% sure this tool is either malware, scam or fake. 1. This software is closed source. 2. The video mention udrop.com to download the application, but link on video description provide download link at mediafire.com and mega.nz instead. For reference, i checked the application based on mediafire.com link. 3. The application was compressed into .rar file with password. This is fairly common method to share pirated software or malware. 4. The application claim to search for ownerless wallet, but doesn't mention location of the wallet file. 5. This application seems to have ability to find seed phrase based on Bitcoin address (video duration 2:53), which is IMPOSSIBLE. 6. The .exe file is flagged by 21 AV. See https://www.virustotal.com/gui/file/13ab2aa012971573519748407a9fe49bb8ae87e85486dcd91f8f593ca672d8ff/detection. but all of these p2p dexs they got tons of people wanting to buy using these crappy unsafe payment methods. unsafe to the seller! My favorite DEX - Bisq - purposefully does not allow people to use methods such as PayPal which can easily be reversed. Bisq also has security deposit requirements to protect both party. |
|
|
|
HI, Who can rewrite the program so that it search for the privat keys from the file .txt ?
or mask generation
I don't know what do you mean by "mask generation", but for .txt file you could create .bat file to parse/loop parameter on .txt file and then execute BitCrack. i pay....
You could create a thread on Services to seek people who can do the job. how is possible that high puzzles already cracked in this high bit range
70 , 75 , 80 , 85 , 90 , 95 , 100 , 105 , 110 , 115
and why 120 and 125 and 130 unsolved
The author of the puzzles release the publickey by doing some small spending in those puzzles. Those were solved with kangaroo or some other tools. The 120 bit puzzle and above are really big and the cost to solve those puzzles is bigger than they worth. To be more specific, those algorithm (such as Pollad's Kangoroo and BSGS) have time complexity lower than O(2^bits). For example, Pollad's Kangoroo time complexity O(sqrt(2^bits)). |
|
|
|
The only real reason this would still be used is for fun or if you have somehow access to a botnet or malware and can run this for free on the victims computer. But even then it is not really profitable and also very illegal for just a small profit. Still nice that it can be done, since CPU mining is the form of mining that satoshi Nakamoto intended for bitcoin. As far as I know he never really though about asics.
Even those who create malware/botnet would mine different coin (usually Monero) which could be mined with CPU at profit. Imagine if someone re-wrote older code or created new code for a GPU / CPU miner program that was able to improve the efficiency drastically of GPU's/ CPU's to compete with smaller Asics. Then what would you say?
Impossible? I don't believe so. Does such code exist currently? No... But one doesn't know for certain what the future will bring.
If it's truly possible, Intel would rather optimize source code of their dedicated GPU[1] driver and modify existing open source SHA-256 mining software rather than creating ASIC[2]. [1] https://www.intel.com/content/www/us/en/products/details/discrete-gpus/arc.html[2] https://www.intel.com/content/www/us/en/products/docs/blockchain/custom-asic-product-brief.html |
|
|
|
|
Show Posts
