|
wallet version is 60400 when i dump with pywallet it shows timestamp alongside the public key… no private key.
i tried dumping every hex value of the binary \x04\x20 followed by(32) as a last resort and did basic compressed and uncompressed versions of the hex values and it doesn’t show.
i also probably tried every thing imaginable, i’m sure the wallet file has the solution to spending the utxo but i think the bitcojn client/litecoin and others i tried seem to ignore it, had anyone else had this issue and sorry my english is bad because i’m so tired of looking for solutions.
btw, check my history in the crypto scene if you think i might waste your time.
|
|
|
|
|
You all are ungrateful and forgetful people. enjoy.
|
|
|
|
Does anyone know where I can find information on the cost for building an delayed quantum eraser setup?
Try Reddit, the community there has everything you can ever imagine  |
|
|
|
Create a USB with kali linux, (it comes prebundled with testdisk and other tools) start kali linux live usb on the device and create a system image with testdisk of the hard disk the wallet existed in. if you value any chance of recovering crypto (and there is loads of methods yet untested such as https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15947 that shows bitcoin-qt creates a crash log with current state i believe of the event of crashing. and the file won't show up with normal scans. Whatever it is you want to do, if you dont make a clone of this hard disk you will regret it. i have done this countless times. The cloned file image of the disk can be used just as the hard drive without any of the weakness. imagine loading it in nvme ssd and now you have 100x the read/write speed or more "5. Delivery it to the pros at Wallet Recovery Services (not sure if they accept forensic cases)" i hear this guy is a selective scammer, he shows up everywhere you look for wallet recovery but he can't do shit. |
|
|
|
|
3 billion? wow i can't believe they are promoting such a small wordlist it's so easy to find a larger torrent.
|
|
|
|
... But what if the time traveler was always in the past as well as the present or future?
The problem is answered in the Bible. Now don't go all nuts on me. I'm not preaching. I am showing you how the problem is talked about in the Revelation. The Revelation tells us that the tail of the dragon swept a third of the stars out of the sky, and flung them to the earth. What is really happening is this:
The stars being talked about are the the angels. The angels are the laws of physics. The dragon is some form of REAL chaos that destroyed a third of the laws of physics. Yet the universe did not collapse. Why not? Jesus.
Now don't go nuts on me again, thinking I am talking about salvation and the cross. All I am saying is that the Revelation is talking about something that was built right into the universe. And when the tail of the dragon destroyed a third of the physics, there was a backup - we call It/Him "Jesus" - that kept the universe working even though a third of the physics had been destroyed.
While time is only part of the "equation," the backup was built right into the universe like a time traveler who went back into the past. The time traveler would have always been in the past at the place where he went back to. It's simply that he wasn't understood to exist back then by those who existed back then, or he was entirely hidden from their eyes.
In the same way, the missing chunk (1/3) of physics was always there in a form that the dragon didn't recognize, or that was hidden from the dragon somehow.
What this means is that all of the past is available to us right now, and maybe all of the present and future. But it is hidden from our eyes, from our understanding. If we could tweak our minds just slightly, we could have all the time travel, and anything else, that we wanted.
But we need to be careful. If we change things, there just might be a backup that will knock us right out of the picture to keep things from changing.
Check the article at the site. Those researchers seem to not be thinking about this at all. Yet the Revelation record seems to be talking this way... a BACKUP.
Scientists Have Shown There's No 'Butterfly Effect' in the Quantum WorldOf all the reasons for wanting to time-travel—saving someone from a fatal mistake, exploring ancient civilizations, gathering evidence about unsolved crimes—recovering lost information isn't the most exciting. But even if a quest to recover the file that didn't auto-save doesn't sound like a Hollywood movie plot, we've all had moments when we've longed to go back in time for exactly that reason.
Theories of time and time-travel have highlighted an apparent stumbling block: time travel requires changing the past, even simply by adding in the time traveller. The problem, according to chaos theory, is that the smallest of changes can cause radical consequences in the future. In this conception of time travel, it wouldn't be advisable to recover your unsaved document since this act would have huge knock-on effects on everything else.  what does it say on https://reddit.com/r/litecoin next to my nick? i have no idea who put that there |
|
|
|
Project relaunch planned soon  |
|
|
|
COIN
Cryptocurrency for real world applications
|| 60 seconds blocktime || 1,200,000,000 COIN || Kimoto Gravity Well ||
COIN:is a general cryptocurrency aiming for real world application. In this world where new altcoins are appearing daily, COIN is taking a place missed by almost every altcoin issued today. A real world application of cryptocurrency. Most of the altcoins have funny or silly name, or name that is made up purely for speculation. Be honest to yourself and try to imagine using cryptocurrency in real world. Are you using animal named coin? Funny or silly named coin? Are you using beercoin for buying beer, breadcoin for buying bread and milkcoin for a milk? Or you are using just one coin? A general purpose coin like COIN? COIN is ready for all your needs, for beer, for bread and milk. It's ready for all merchandise and all products available, not just specific products. Coin is made for real world applications, not just speculation.
COINSymbol: COIN Symbol: ₡ PoW algorithm: Scrypt Retarget: Kimoto Gravity Well Blocktime: 60 seconds Transactions: 3 confirmations Coin Maturity: 30 confirmations Max supply: 1,200,000,000 COIN Premine: less than 1% (11,500,000 COIN) RPC: 24055 P2P: 24057 ExchangesBTC: C-Cex https://c-cex.com/index.html?p=coin-btcUSD: C-Cex https://c-cex.com/index.html?p=coin-usdExchanges coming soon (SUPPORT COIN BY VOTING)MintPal https://www.mintpal.com/votingCryptoALTeX https://www.cryptoaltex.com/index.php?page=newcoinCryptokk.com http://www.cryptokk.com/?p=votesCrypto Rush https://cryptorush.in/index.php?p=voteSites that accept COINCOIN Dice http://coindice.supercrypt.co/IRC:Freenode #coin-project Block rewards:block < 140: 2 COINblock < 131487: 1000 COIN // three months block < 262974: 900 COIN // six months block < 394461: 800 COINblock < 525948: 700 COIN // one year block < 657435: 600 COINblock < 788922: 500 COINblock < 920409: 400 COINblock < 1051896: 300 COIN // two years block < 1183383: 200 COINblock < 1314870: 100 COINblock < 1446357: 90 COINblock < 1577844: 80 COIN // three years block < 1709331: 70 COINblock < 1840818: 60 COINblock < 1972305: 50 COINblock < 2103792: 40 COIN // four years block < 2235279: 30 COINblock < 2366766: 20 COIN // four years six months block > 2366766: 10 COIN // approx. eighty four years Downloads:Source: https://github.com/coin-project/coin.gitWindows wallet: https://docs.google.com/uc?id=0B3lBEhr0wF7qZ0daV0VtNHF5Ync&export=downloadMac OS X COIN wallet https://docs.google.com/uc?id=0ByOpAME8KeimMXVhd3djczdMZVk&export=downloadP2Pool: https://github.com/coin-project/p2pool-rav.gitP2Pools:US node: http://p2pool-us.coin-project.org:24002/ 1.5% EU node: http://p2pool-eu.coin-project.org:24002/ 1.5% EU node: http://theminingcrew.com:24002/ 1% by mrT2k14ASIA node: http://kopivienna.no-ip.biz:24002/ 1.5% by ShuxyURL: p2pool-us.coin-project.org:24002 Username: YourCoinAddress Password: xP2Pool: Decentralized mining pool, using P2Pool helps keeping network healthy P2Pool: If you want to run your own P2Pool node, use https://github.com/coin-project/p2pool-rav.git (start it with an argument -n 188.226.185.251) MPOS Pools:Pool: http://www.coin-mining.org/ 1% PROP, stratum by litecoin_messiahPool: http://coin.crypto-hamsters.com/ ?%, by crypto-hamsterPool: http://coin.fedaykin.us/ 0.8%, stratum, vardiff, by edricOther sites:Abe block explorer: http://explorer.coin-project.org/CryptoCoin Charts: http://www.cryptocoincharts.info/v2/coins/show/coinCoinmarketcap.com: http://coinmarketcap.com/all.html#coinWhatMine.com: http://whatmine.com/coin/368/Coin-COIN-Scrypt-ProfitabilityCoin.conf:Please mind capital C in Coin.conflisten=1
server=1
daemon=1
rpcuser=USER
rpcpassword=PASSWORD
addnode=107.170.70.40
addnode=188.226.185.251
addnode=188.226.184.38
addnode=coin-mining.org |
Fair launch:- no mega announcement to create hysteria, everyone have fair chance to start mining, no mega GPU farms on start - Kimoto Gravity Well from the start - P2Pool, decentralized mining pool from the start
|
|
|
|
Has the blockchain been forked?
No, there is no reason for this. Just checking, my pool has an issue which i'm trying to debug need to rule this out. |
|
|
|
|
Has the blockchain been forked?
|
|
|
|
|
Yes, There will also be many security issues relating to it.
|
|
|
|
IMHO Better create your coin if you want your own algo. At the time of this means you do not have the ability to handle a coin and prefer to take the hard job of others(devs, community, minners, investors) and a stable user base, just my opinion don't hate me  These idiots think they can fork the litecoin change, fuck it rare possibility they will they choose x11, something that isn't even tested properly yet. No point making Litecoin ASIC proof, the real aim is having the ASIC's diversified. I do whatever in my power i can to discourage the promotion of PRE-Orders happening, once we keep it this way it's unlikely we will have another BFLabs fiasco happening. |
|
|
|
|
LOL you ain't doing this for Litecoin mate, not as long as i'm breathing/
|
|
|
|
Thanks. If my miner has a sharediff set to 10, I (should) get 10x the credit every time I submit a share. The rules vary by pool. OK, I get it, but the range (e.g. sharediff from 1 to e.g. 100) is up to the pool creator yes? Or is there maybe a consensus/well established rules about it? Edit: or maybe there is no reason to set the maximum of it? 65536 is the average number of hashes to be computed in order to find a 1 share at mining difficulty 1 for a bitcoin based coin. When the pool sets the share-diff to something higher, for example at share diff 10, your miner has to hash 10x more to find that share on average. So 655360 hashes at share diff 10 and 65536 hashes at share diff 1. Pools with vardiff or anything similar adjust the share diff to something like 512, because miners with 100's of khashs will have to make more connections to the stratum server at a lower mining difficulty resulting a higher risk of shares being lost. If they send shares at a higher difficulty they will be submitting work less often and have less stales. Dunno why i'm explaining this or even if it was necessary, i haven't slept so excuse me  Thanks, but now I'm completely lost  Why 65536? Why this *constant*? Doesn't it depend on current network difficulty? And - why sending sending shares less often results in lower risk of shares being lost? Network latency and stuff like that cause disruptions in connections now and then. dunno i'm very tired. |
|
|
|
Thanks. If my miner has a sharediff set to 10, I (should) get 10x the credit every time I submit a share. The rules vary by pool. OK, I get it, but the range (e.g. sharediff from 1 to e.g. 100) is up to the pool creator yes? Or is there maybe a consensus/well established rules about it? Edit: or maybe there is no reason to set the maximum of it? 65536 is the average number of hashes to be computed in order to find a 1 share at mining difficulty 1 for a bitcoin based coin. When the pool sets the share-diff to something higher, for example at share diff 10, your miner has to hash 10x more to find that share on average. So 655360 hashes at share diff 10 and 65536 hashes at share diff 1. Pools with vardiff or anything similar adjust the share diff to something like 512, because miners with 100's of khashs will have to make more connections to the stratum server at a lower mining difficulty resulting a higher risk of shares being lost. If they send shares at a higher difficulty they will be submitting work less often and have less stales. Dunno why i'm explaining this or even if it was necessary, i haven't slept so excuse me |
|
|
|
|
Show Posts
