Ninjastic
Search content
Sort by
Showing 8 of 8 results by kewa07
Post
Topic
Board Project Development
Re: Keyhunt - development requests - bug reports
by
kewa07
on 18/07/2023, 13:24:48 UTC
Quote from: albert0bsd on July 13, 2023, 08:37:34 PM
There is an example of the address format in the documentation, please check it.

About the speed, the hashing process for eth it is more slow than the process for Bitcoin. Also there are some calculations that can't be avoided for eth, and those calcs can be avoided for Bitcoin address then  it will be more slow for eth than bitcoin



Thank you
Is it possible to change the search step, for example, not 00001 - 00002 - 00003, but 01000 - 02000 - 03000 Huh
Post
Topic
Board Development & Technical Discussion
Re: BitCrack - A tool for brute-forcing private keys
by
kewa07
on 18/07/2023, 10:46:05 UTC
Quote from: neirobobi on Today at 09:20:30 AM
Quote from: kewa07 on July 17, 2023, 11:22:03 AM
tell me, is it possible to use bitcrack for Ethereum? Huh

you need AltCrack


does it work with ethereum? you need hash160, and the ether address is created differently
Post
Topic
Board Development & Technical Discussion
Re: BitCrack - A tool for brute-forcing private keys
by
kewa07
on 17/07/2023, 11:22:03 UTC
tell me, is it possible to use bitcrack for Ethereum? Huh
Post
Topic
Board Project Development
Re: Keyhunt - development requests - bug reports
by
kewa07
on 13/07/2023, 17:44:31 UTC
Tell me how to use eth mode, when reading addresses from a file, it gives an error Sad
Post
Topic
Board Bitcoin Technical Support
Re: non-standard segwit(BECH32) transaction
by
kewa07
on 20/12/2021, 10:27:31 UTC
Quote from: nc50lc on Today at 09:10:08 AM
You can try to contact the same miner (mining pool) who mined the transaction (page8) if he'll agree to your offer.

wrote in PM, but no one answered that way(
Post
Topic
Board Bitcoin Technical Support
Re: non-standard segwit(BECH32) transaction
by
kewa07
on 20/12/2021, 10:10:51 UTC
wrote in PM, but no one answered that way (
Post
Topic
Board Development & Technical Discussion
Re: non-standard segwit(BECH32) transaction
by
kewa07
on 19/12/2021, 18:32:25 UTC
coinb.in service signed the transaction without any problems, and it is broadcast to live.blockcypher.com, but to no avail
https://live.blockcypher.com/btc/tx/cff034409db3a02a6d1a9a1708ecaf7414381d19ba0ca4defd32d5d465e6f5cd/
I got acquainted with the segwit protocol, and realized that the transaction is non-standard, but there have already been cases that such transactions go through (link in the post)
Post
Topic
Board Development & Technical Discussion
Merits 5 from 2 users
Topic OP
non-standard segwit(BECH32) transaction
by
kewa07
on 19/12/2021, 17:56:55 UTC
⭐ Merited by LoyceV (4) ,ETFbitcoin (1)
There is an address generated with an uncompressed private key. When trying to withdraw funds, the network rejects (Invalid transaction. Error: non-mandatory-script-verify-flag (Using non-compressed keys in segwit))
Maybe someone can help me push the transaction, like in this post:

https://bitcointalk.org/index.php?topic=5192454.0

generated transaction with a commission to the miner 0.001 BTC:


0100000000010147fb8361a9808f371f45f3a9e98584d02a322b2694ff179deb32381e7a560bf00 000000000fdffffff0140ef070000000000160014510942beb6e2b4c297647f9a5840647db74e64 0d0247304402206331c747313e4d69fef2e0835abc11e3ae49b026f2c2e53ca8b989b2490c43410 220319527569dbffff072e0a85adab432d176d260199a43ac456e2bdecb3d8e7272014104c56e7b 928bb8400c8dbaeffc3de9d074969f97ababc11be86042e5da5f46233e857ba6c40bf58ca2d7453 2615fdeb91c0e5251822a6879b140f72ca1be8337c500000000