|
Is there any interest in resurrecting the old Megacoin android app by Hash Engineering?
Does anyone have any coins that are stuck in that app that need to be retrieved?
According to my records, there are 15 people with this app still installed.
|
|
|
|
|
Is there any interest in resurrecting the Myriad android app by Hash Engineering?
Does anyone have any coins in that app that they need to get out. It currently doesn't work, so the coins are stuck unless you found a way to get your private keys out of it. Yes, there is a way, but it isn't easy.
|
|
|
|
The block reward code is as follows: int64 static GetBlockValue(int nHeight, int64 nFees)
{
int64 nSubsidy = 524288 * COIN;
// Subsidy is cut in half every 86400 blocks, which will occur approximately every 1 month
nSubsidy >>= (nHeight / 86400); // Infinitecoin: 86400 blocks in ~1 month
return nSubsidy + nFees;
} The halving is every month (based on 30 second blocks). After 64 months, the halving number appears to return to 0 based on the undefined behavior of a 64bit number being right shifted 64 bits. According to the C++ language, this operation has undefined results -- this means that the result could be different on different machines/CPU's. If there are differences this could lead to forks or clients and apps that do not sync past 5529600. This will require a hard fork fix on the code above. At a certain block height in the future, this code would be modified to force the reward to be zero. |
|
|
|
Still service for android wallet?
Yes, but due to demand, I am expensive. |
|
|
|
|
I might be willing to update the app on the Google Play store, the code changes look minimal on the POW change, but many other things are out of date on this software.
I am rather busy, but in a few weeks can consider working on it again.
Ideally, the code should be scrapped nearly and started fresh with Bitcoin Wallet 6.x and bitcoinj 0.15 once segwit is finally added.
|
|
|
|
|
The android wallet may be having issues. Not sure what the problem is now, but some users are reporting crashes while others cannot send or sync their wallets after restoring.
We are looking into it.
|
|
|
|
Hey guys.
Unobtanium wallet for Android.
I am trying to restore a backup file with the Unobtanium Wallet which was created by the wallet. When I try to restore, by opening the backup file with the app, I enter my password and get a success screen, but the UNO never appears in my wallet.
Also, when trying to send UNO from the wallet it just doesn't work.
Is there a way to get the private key / decrypt the backup file so that I can sweep the wallet into another wallet?
Please help I'm very concerned.
This sounds like this app is not connecting to the UNO network, so it cannot determine your balance. Sending will not work either if there is no network connection. Currently my app is connecting to one peer, but it is not syncing the blockchain. DECRYPTING YOUR WALLET FILE. You will need a PC with openssl and git. And your backup file. You now have your backup file on your PC. Wallet backups are encrypted. Let's decrypt it using: openssl enc -d -aes-256-cbc -a -in unobtanium-wallet-backup-2014-11-01 > unobtanium-wallet-decrypted-backup It will ask you for a decryption password, which is your backup password. If it prints "bad password" you've got the wrong password, but if it doesn't print anything your password might still be wrong. We can only be sure by looking at the decrypted data. RECOVERING FROM PROTOBUF WALLET FORMAT We need wallet-tool from bitcoinj. First, in a working directory, let's get bitcoinj: git clone -b release-0.12 https://github.com/hashengineering/unobtaniumj.gitMake sure everything is compiled and ready to go by using once: cd unobtaniumj/tools ./wallet-tool Now use wallet-tool to sync the wallet from your backup: ./wallet-tool reset --wallet=unobtanium-wallet-decrypted-backup ./wallet-tool sync --wallet=unobtanium-wallet-decrypted-backup --debuglog The sync process will take anywhere from a few minutes to hours. Wallet-tool will return to the shell prompt if its finished synching. Have a look at the wallet: ./wallet-tool dump --wallet=/tmp/bitcoin-wallet-decrypted-backup --dump-privkeys You can skip the sync to the wallet if you don't think you received any coins in new addresses since you made your last backup. The last command will dump onto the screen all your private keys and your seed (12 word recovery phrase). The phrase may be able to be used in other unobtainium software that can read BIP32 / BIP39 phrases. Good Luck. |
|
|
|
I was thinking about doing primecoin a while back. It has a different POW than other coins that I have done, and that would be a challenge. Unfortunately, I don't have time to work on it. |
|
|
|
|
Does anyone use the android app anymore? We have users that have Android 7 devices that cannot use the app because it always crashes. The fix has been found, but not implemented.
|
|
|
|
|
Support for the android app Digitalcoin Wallet has discontinued. It has been taken down from Google Play.
We don't have time to maintain this any future in light of our other projects.
|
|
|
|
TYVM!
I was a bit concerned my phone was more damaged than previously assumed..
next topic - How much would an IXC android wallet cost?
(opinions on IXC welcome)
Our price hasn't change in over 2 years - 1 BTC per wallet. |
|
|
|
It is true that the Quark Wallet for android has been updated by Hash Engineering (as that is me). Many users have reported several problems such as freezing screens and on older android devices the app never syncs with the Quark Blockchain (meaning it takes forever). For instance on my own Android 4 and 7 devices (app installed on June 21) it has been nearly two weeks and it is only at block 3 million. This could be fixed with an update to the app by building a checkpoints file. Unfortunately, building of the checkpoints file (requires downloading the blockchain from a client on the same machine and saving headers to a file) is also taking forever on both of my development machines. Based on my own work, I don't know if new users can get this app to work. If Quark is changing to a POW/POS hybrid that will definitely break the app if it isn't already broken. The app will not support any POS blocks. As soon as one is included in the blockchain, the app will reject it and the app will be stuck on the previous block. Fixing that will require a ton of work (it has been done by the peercoin developer), but it requires a special block explorer (also made by the peercoin wallet for android developer). Hash Engineering will not be doing this upgrade.
The bottom line is that given this knowledge, users should transfer their coins from the Quark Wallet app to other addresses maintained in other Quark wallets.In the near future I will be taking the Quark Wallet app off the Google Play store to prevent new users from losing coins. But is it possible for the right bounty? Depending on the success of the qrk come back right now in progress could you do this if required for the right reward? How much would you have to do from scratch and how much could we borrow from ppc? Sure the right bounty can fix it. However, the special block explorer is not something that I do. Many have asked for POS wallets for android and none have provided a working block explorer for the app to use. This project will require several expert developers. |
|
|
|
It is true that the Quark Wallet for android has been updated by Hash Engineering (as that is me). Many users have reported several problems such as freezing screens and on older android devices the app never syncs with the Quark Blockchain (meaning it takes forever). For instance on my own Android 4 and 7 devices (app installed on June 21) it has been nearly two weeks and it is only at block 3 million. This could be fixed with an update to the app by building a checkpoints file. Unfortunately, building of the checkpoints file (requires downloading the blockchain from a client on the same machine and saving headers to a file) is also taking forever on both of my development machines. Based on my own work, I don't know if new users can get this app to work. If Quark is changing to a POW/POS hybrid that will definitely break the app if it isn't already broken. The app will not support any POS blocks. As soon as one is included in the blockchain, the app will reject it and the app will be stuck on the previous block. Fixing that will require a ton of work (it has been done by the peercoin developer), but it requires a special block explorer (also made by the peercoin wallet for android developer). Hash Engineering will not be doing this upgrade.
The bottom line is that given this knowledge, users should transfer their coins from the Quark Wallet app to other addresses maintained in other Quark wallets.In the near future I will be taking the Quark Wallet app off the Google Play store to prevent new users from losing coins. |
|
|
|
I was able to get my coins out of my wallet from the client that crashed on windows by building the client for linux. Has anyone had any luck building for Windows. I still can't get a build on Mac. |
|
|
|
Compiling on MacOS 10.12, there is a different error from a missing boost function while linking. boost::this_thread::hiden::sleep_for Boost 1.63 is installed on my mac using homebrew. Still looking into a resolution. |
|
|
|
Has anyone tried building the source for Windows yet? If not, I will give it a go this weekend. I've been working on a new site for DGC, takes a lot of time.
I tried building on linux and Mac, but not Windows. With Linux (Ubuntu 16.04), there was a compile issue that was resolved. ./autogen.sh
configure.ac:707: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
configure.ac:707: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
configure.ac:707: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
configure.ac:707: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
configure.ac:707: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
CXX rpcrawtransaction.o
In file included from /usr/include/boost/move/detail/type_traits.hpp:34:0,
from /usr/include/boost/move/core.hpp:54,
from /usr/include/boost/move/utility_core.hpp:29,
from /usr/include/boost/move/utility.hpp:28,
from /usr/include/boost/thread/detail/move.hpp:27,
from /usr/include/boost/thread/lock_types.hpp:11,
from /usr/include/boost/thread/pthread/mutex.hpp:16,
from /usr/include/boost/thread/mutex.hpp:16,
from allocators.h:13,
from serialize.h:9,
from bignum.h:9,
from chainparams.h:9,
from base58.h:17,
from rpcrawtransaction.cpp:6:
/usr/include/boost/variant/get.hpp: In instantiation of ‘typename boost::add_reference<T>::type boost::strict_get(boost::variant<T0, T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19>&) [with U = const CScriptID&; T0 = CNoDestination; T1 = CKeyID; T2 = CScriptID; T3 = CStealthAddress; T4 = boost::detail::variant::void_; T5 = boost::detail::variant::void_; T6 = boost::detail::variant::void_; T7 = boost::detail::variant::void_; T8 = boost::detail::variant::void_; T9 = boost::detail::variant::void_; T10 = boost::detail::variant::void_; T11 = boost::detail::variant::void_; T12 = boost::detail::variant::void_; T13 = boost::detail::variant::void_; T14 = boost::detail::variant::void_; T15 = boost::detail::variant::void_; T16 = boost::detail::variant::void_; T17 = boost::detail::variant::void_; T18 = boost::detail::variant::void_; T19 = boost::detail::variant::void_; typename boost::add_reference<T>::type = const CScriptID&]’:
/usr/include/boost/variant/get.hpp:284:25: required from ‘typename boost::add_reference<T>::type boost::get(boost::variant<T0, T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19>&) [with U = const CScriptID&; T0 = CNoDestination; T1 = CKeyID; T2 = CScriptID; T3 = CStealthAddress; T4 = boost::detail::variant::void_; T5 = boost::detail::variant::void_; T6 = boost::detail::variant::void_; T7 = boost::detail::variant::void_; T8 = boost::detail::variant::void_; T9 = boost::detail::variant::void_; T10 = boost::detail::variant::void_; T11 = boost::detail::variant::void_; T12 = boost::detail::variant::void_; T13 = boost::detail::variant::void_; T14 = boost::detail::variant::void_; T15 = boost::detail::variant::void_; T16 = boost::detail::variant::void_; T17 = boost::detail::variant::void_; T18 = boost::detail::variant::void_; T19 = boost::detail::variant::void_; typename boost::add_reference<T>::type = const CScriptID&]’
rpcrawtransaction.cpp:299:77: required from here
/usr/include/boost/variant/get.hpp:178:5: error: invalid application of ‘sizeof’ to incomplete type ‘boost::STATIC_ASSERTION_FAILURE<false>’
BOOST_STATIC_ASSERT_MSG(
^
This issue was resolved by https://github.com/bitcoin/bitcoin/commit/8b08d9530b93c7a98e7387167ecd2cd5b0563bfb. I have seen this error on many coins when compiling on my system. After this is resolved, the qt runs without crashing. |
|
|
|
|
Show Posts
