|
It looks like there may be a problem with the infinitecointalk.org website.
In any case, after doing some research on the other Android Wallets, we have been able to determine how to get more peers connect to the Wallet using IRC discovery and a means of saving peers to a database (like peers.dat). This feature will be included in the next update of the android wallet.
|
|
|
|
We are having success with the DIMEcoin Android Wallet. The blockchain is syncing. The new icon is being used.
We are lacking a block explorer. We are lacking some reliable nodes to connect to. This app will need one or more reliable trustworthy nodes that are always on. I have heard that Amazon EC2 cloud servers are free for one year. Other coin developers have used those types of accounts to set up nodes. At a later point in time, a better method of connecting to nodes may be available.
Thank you, I will look into the amazon servers. I am currently working on the block explorer. It took a while to figure out how to do it properly  The block explorer can serve as a node as well, but another dedicated node will be better to have online for the android wallet. |
|
|
|
|
We are having success with the DIMEcoin Android Wallet. The blockchain is syncing. The new icon is being used.
We are lacking a block explorer. We are lacking some reliable nodes to connect to. This app will need one or more reliable trustworthy nodes that are always on. I have heard that Amazon EC2 cloud servers are free for one year. Other coin developers have used those types of accounts to set up nodes. At a later point in time, a better method of connecting to nodes may be available.
|
|
|
|
|
Work has begun on an Android Wallet for this coin. We are not sure when it will be ready for beta testing, but it will be a fork of the Andreas Schildbach Bitcoin Wallet. So far we are working on the Java back end library for it and have cracked the 5 hash algorithms and the difficulty adjustment code. Syncing with the blockchain appears to be working.
|
|
|
|
|
The new website indicates that Dimecoin is an SHA-3 coin. Is there a plan to switch to an SHA-3 only hash, or am I being over technical in pointing out that Dimecoin uses 6 of the SHA-3 candidates, including the winner Keccak?
|
|
|
|
|
Version 0.1.12 has been posted to Google Play. Syncing will be faster for new users.
|
|
|
|
After looking at the github, it appears that you have commented out the lines for PeerDBDiscovery. It should be working now.
Ideally that should be working as the Litecoin team has it working in their app. I wanted to add it to my apps as well.
do you know what's the major different betwee the current megacoin and litecoin resp? I am also trying to make the android wallet. but seems litecoin wallet has no KGW impl. The current litecoin app is forked from the bitcoin wallet. The megacoin app is a fork of the digitalcoin app which is a fork of the bitcoin wallet. The code base is very similar. You could take the KGW code from the Megacoinj library and place it into the Litecoin bitcoinj module. I even wrote a native implementation of KGW. you can PM me if you have further questions as I wrote the java code for KGW. |
|
|
|
Is there a working block explorer for Dimecoin? The app will need one for some features. It is also useful during the debugging process. |
|
|
|
|
This bounty is about $88 and is not enough to pay a developer. Such a task takes a month or two to verify that the wallet is secure and reliable.
|
|
|
|
|
This issue was resolved by specifying the correct parameters for the Genesis Block.
|
|
|
|
|
After looking at the github, it appears that you have commented out the lines for PeerDBDiscovery. It should be working now.
Ideally that should be working as the Litecoin team has it working in their app. I wanted to add it to my apps as well.
|
|
|
|
Here are the changes to the LitecoinParams that will resolve the error in the OP: diff --git a/core/src/main/java/org/litecoin/LitecoinParams.java b/core/src/main/java/org/litecoin/LitecoinParams.java
index c33b770..1bf631a 100644
--- a/core/src/main/java/org/litecoin/LitecoinParams.java
+++ b/core/src/main/java/org/litecoin/LitecoinParams.java
@@ -38,7 +38,7 @@ public class LitecoinParams extends NetworkParameters {
id = "org.litecoin.production";
proofOfWorkLimit = Utils.decodeCompactBits(0x1e0fffffL);
addressHeader = 15;
- acceptableAddressCodes = new int[] { 48 };
+ acceptableAddressCodes = new int[] { 15 };
port = 12622;
packetMagic = 0xfbc0b6dbL;
dumpedPrivateKeyHeader = 128 + addressHeader;
@@ -54,15 +54,15 @@ public class LitecoinParams extends NetworkParameters {
try {
// A script containing the difficulty bits and the following message:
//
- // "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks"
+ // "Irish universities fail to make list of top 100 institutions"
byte[] bytes = Hex.decode
- ("0497269736820756e69766572736974696573206661696c20746f206d616b65206c697374206f6620746f702031303020696e737469747574696f6e73");
+ ("04ffff001d01043c497269736820756e69766572736974696573206661696c20746f206d616b65206c697374206f6620746f702031303020696e737469747574696f6e73");
t.addInput(new TransactionInput(this, t, bytes));
ByteArrayOutputStream scriptPubKeyBytes = new ByteArrayOutputStream();
Script.writeBytes(scriptPubKeyBytes, Hex.decode
("040184710fa689ad5023690c80f3a49c8f13f8d45b8c857fbcbc8bc4a8e4d3eb4b10f4d4604fa08dce601aaf0f470216fe1b51850b4acf21b179c45070ac7b03a9"));
scriptPubKeyBytes.write(ScriptOpCodes.OP_CHECKSIG);
- t.addOutput(new TransactionOutput(this, t, Utils.toNanoCoins(50, 0), scriptPubKeyBytes.toByteArray()));
+ t.addOutput(new TransactionOutput(this, t, Utils.toNanoCoins(25, 0), scriptPubKeyBytes.toByteArray()));
} catch (Exception e) {
// Cannot happen.
throw new RuntimeException(e); However, there is still another exception: 04-26 21:17:53.514 2633-2692/de.schildbach.wallet_ltc E/AndroidRuntime﹕ FATAL EXCEPTION: PeerGroup
java.lang.RuntimeException: java.io.IOException: pipe failed: EMFILE (Too many open files)
at com.google.bitcoin.net.NioClientManager.<init>(NioClientManager.java:85)
at com.google.bitcoin.core.PeerGroup.<init>(PeerGroup.java:207)
at com.google.bitcoin.core.PeerGroup.<init>(PeerGroup.java:199)
at org.litecoin.LitcoinPeerDBDiscovery$PeerGroupWrapper.<init>(LitcoinPeerDBDiscovery.java:75)
at org.litecoin.LitcoinPeerDBDiscovery$PeerGroupWrapper.<init>(LitcoinPeerDBDiscovery.java:71)
at org.litecoin.LitcoinPeerDBDiscovery.<init>(LitcoinPeerDBDiscovery.java:86)
at de.schildbach.wallet.service.BlockchainServiceImpl$3$1.getPeers(BlockchainServiceImpl.java:425)
at com.google.bitcoin.core.PeerGroup.discoverPeers(PeerGroup.java:502)
at com.google.bitcoin.core.PeerGroup.connectToAnyPeer(PeerGroup.java:556)
at com.google.bitcoin.core.PeerGroup.run(PeerGroup.java:534)
at com.google.common.util.concurrent.AbstractExecutionThreadService$1$1.run(AbstractExecutionThreadService.java:52)
at java.lang.Thread.run(Thread.java:856)
Caused by: java.io.IOException: pipe failed: EMFILE (Too many open files)
at java.nio.SelectorImpl.<init>(SelectorImpl.java:99)
at java.nio.SelectorProviderImpl.openSelector(SelectorProviderImpl.java:41)
at com.google.bitcoin.net.NioClientManager.<init>(NioClientManager.java:83)
at com.google.bitcoin.core.PeerGroup.<init>(PeerGroup.java:207)
at com.google.bitcoin.core.PeerGroup.<init>(PeerGroup.java:199)
at org.litecoin.LitcoinPeerDBDiscovery$PeerGroupWrapper.<init>(LitcoinPeerDBDiscovery.java:75)
at org.litecoin.LitcoinPeerDBDiscovery$PeerGroupWrapper.<init>(LitcoinPeerDBDiscovery.java:71)
at org.litecoin.LitcoinPeerDBDiscovery.<init>(LitcoinPeerDBDiscovery.java:86)
at de.schildbach.wallet.service.BlockchainServiceImpl$3$1.getPeers(BlockchainServiceImpl.java:425)
at com.google.bitcoin.core.PeerGroup.discoverPeers(PeerGroup.java:502)
at com.google.bitcoin.core.PeerGroup.connectToAnyPeer(PeerGroup.java:556)
at com.google.bitcoin.core.PeerGroup.run(PeerGroup.java:534)
at com.google.common.util.concurrent.AbstractExecutionThreadService$1$1.run(AbstractExecutionThreadService.java:52)
at java.lang.Thread.run(Thread.java:856)
Caused by: libcore.io.ErrnoException: pipe failed: EMFILE (Too many open files)
at libcore.io.Posix.pipe(Native Method)
at libcore.io.ForwardingOs.pipe(ForwardingOs.java:94)
at java.nio.SelectorImpl.<init>(SelectorImpl.java:92)
at java.nio.SelectorProviderImpl.openSelector(SelectorProviderImpl.java:41)
at com.google.bitcoin.net.NioClientManager.<init>(NioClientManager.java:83)
at com.google.bitcoin.core.PeerGroup.<init>(PeerGroup.java:207)
at com.google.bitcoin.core.PeerGroup.<init>(PeerGroup.java:199)
at org.litecoin.LitcoinPeerDBDiscovery$PeerGroupWrapper.<init>(LitcoinPeerDBDiscovery.java:75)
at org.litecoin.LitcoinPeerDBDiscovery$PeerGroupWrapper.<init>(LitcoinPeerDBDiscovery.java:71)
at org.litecoin.LitcoinPeerDBDiscovery.<init>(LitcoinPeerDBDiscovery.java:86)
at de.schildbach.wallet.service.BlockchainServiceImpl$3$1.getPeers(BlockchainServiceImpl.java:425)
at com.google.bitcoin.core.PeerGroup.discoverPeers(PeerGroup.java:502)
at com.google.bitcoin.core.PeerGroup.connectToAnyPeer(PeerGroup.java:556)
at com.google.bitcoin.core.PeerGroup.run(PeerGroup.java:534)
at com.google.common.util.concurrent.AbstractExecutionThreadService$1$1.run(AbstractExecutionThreadService.java:52)
at java.lang.Thread.run(Thread.java:856) This error is a result of some changes the Litecoin Dev Team made to the bitcoin code. I also had this problem when I imported their PeerDBDiscovery class into one of my android apps. Catching this RuntimeException does not solve the problem, but locks up the app. This error does not happen immediately, but after a period of time. Perhaps the pipes are not being closed? At this time, I don't have a solution for it, except to remove it and use DnsDiscovery instead. |
|
|
|
|
I will take a look at this soon, as I have been able to fix many bugs in these apps.
The exception generated appears to be from the initialization of a static Property of the Constants class, which is probably because the genesis block is not configured correctly to match the hash.
|
|
|
|
|
We are currently considering working on Coins that use X11 and the Dark Gravity Wave. Someone has to write this code and it might as well be us.
As of today, we have successfully tested the X11 algorithm (in Java) and the Dark Gravity Wave (1 and 2).
Nothing has been done on native versions of these for android, yet.
|
|
|
|
|
Neither is it a quick thing to fork the bitcoin wallet to another coin. After that there is much maintenance required to keep the app functional given all the updates that coin devs push through.
|
|
|
|
|
At this point, prices are 3 to 4 BTC. However, that price is another way to say we are too busy to take on more projects.
|
|
|
|
Ripple & NXT coins have one. Why can't BlackCoin? Anything is possible in the coding world.. Just have to find the right person Yes, there are always possibilities, but a light standalone wallet would need to be less secure given the limitations and requirements imposed by proof of stake. POS coins, to securely function, need much more data from the blockchain than a POW coin. Conceivably, one could easily fill up all the phone's memory and quickly use up the data plan managing the blockchain. Contrast that to a POW coin, which uses less than 1 MB for the blockchain data and a minimal amount of bandwidth since only block headers are downloaded. An android wallet that uses an online server is the way to go here. Security is a chief concern, once again. |
|
|
|
|
If you are looking for a fork of the bitcoin wallet by Andreas Schildbach, that won't be happening anytime soon. There is a $15,000 bounty for a Peercoin fork, but nothing working has been released.
Proof of stake cannot be implemented as a light or SPV application.
|
|
|
|
|
Show Posts
