-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question - "Electrum Server" #234
Comments
Not that I am aware of. |
You seem to have a dev chop or two :) Why not get involved with the CLAM project? :) |
In some indirect way I am involved. I'm working on the UberPay wallet and my goal is to include as many coins possible that have the potential for consumer/merchant adaptation. It critical that we work harder for adaptation. I hope the CLAM dev community would consider setting up an electrum server. Take a look if you wish at UberPay, I have completed much of the CLAM integration now I need an electrum server to test and release in the community. I do have need some confirmation on these values.
|
Link to some resources concerning the electrum server? I will have xploited or dooglus verify the above values when they get on. |
I will, after 20+ coins things click... 🎯 you may say I came late in the Bitcoin revolution, I've been developing from the glory days late 70s :) now its catch up time 💨 I have a question that may seen silly, can Electrum run multiple coin instances? Still reading up on E between projects. |
Haven't taken a look at Electrum; last I knew it was a Bitcoin SPV wallet. |
I just finish testing the CLAM wallet addresses in the UberPay android http://www.blocktree.io/address/CLAM/xAHyunc9jRdjnhDijUjA5dLRsYfjBdvwWn |
If the CLAMS community is ready to setup a clams electrum server, the UberPay wallet is ready to support it. Something to consider. |
Was this closed out of impatience, or was an electrum server set-up? |
I saw that coinomi or someone with coinomi has setup a server but has issues I tried the coinomi wallet and it does not process CLAM coins. I thought maybe you guys notice the issue. I have a Server monitor for the servers to keep an eye on them to make sure the coins and wallets that use these servers maintain their integrity and trust with the respective coin community. The error is from the CLAm server. 11-01 18:29:48.367 4333-4432/com.mygeopay.wallet E/ServerClient: Could not get reply for blockchain.transaction.get |
Does the CLAM community run a CLAM electrum server separately? Personally I believe its a must for the coin Dev's to have it, if it helps with coin adaptation. |
There isn't any as of yet. I will look into it today though. I can put one The error from coinomi looks like it isn't properly hashing the txid's. I I need to ask another dev from irc about this.. I made a chain with his I will post an update later On Sun, Nov 1, 2015 at 12:38 PM, Adonis Valamontes <[email protected]
|
Its always good to have alt backup, for reliability! If you can do it that On Sun, Nov 1, 2015 at 8:35 PM, l0rdicon [email protected] wrote:
Geopay.me Inc. _"don't need to know everything, I just need to know where to find it."_A. Mobile is direct, accurate, and personal. This email may contain confidential and/or privileged information. If you Email transmission security and error-free status cannot be guaranteed as |
Seems there is a server running now... |
Thats not a clams server its a DOGE server mislabeled! On Sat, Nov 28, 2015 at 10:54 PM, SuBPaR42 [email protected] wrote:
Geopay.me Inc. _"don't need to know everything, I just need to know where to find it."_A. Mobile is direct, accurate, and personal. This email may contain confidential and/or privileged information. If you Email transmission security and error-free status cannot be guaranteed as |
Ahh - apologies... |
Almost a decade later, I am looking to install a CLAMs electrum server but I run into errors during the sync. Was a CLAMs server ever set up/tested? If so, maybe the server source exists somewhere? |
Does anyone know of any CLAM electrum servers up and running?
The text was updated successfully, but these errors were encountered: