ok, it's working perfectly now.

I made this faucet back at 2015 and it always work.

But not until January 2025, my server got wiped due to vps provider (another long story and I'll not post it here), I restore the backup at 20231110, so that we can coutinue the service, both faucet and blockchain explorer, but the problem now it, I cannot catch up the blockchain since no peers was successfully connected, now the block header is stuck at height 610575(2024-05-19 17:06:18), and nothing changed since more than 20hours past. I tried to connect to explorer.devcoin.org but its 52333 port is closed. so any other peers we know are publicly connectable?

I do not familiar with docker under windows, maybe there was some write permission issue or other compatible things...

if your docker installation is complete, just 'docker run emfox/devcoin:testing' will do everything, for detail please reference at:
https://docs.docker.com/docker-for-windows/

hello everyone, I have created an infrastructure of automated building devcoin(only devcoind, no devcoin-qt) on docker hub, that depending on well crafted dockerfile. the latest tag will follow master branch, and any new commit will be at testing tag first, then moved into latest.
Now the newest latest is not available because the new Dockerfile hasn't accept into official repo, and so the build is only tracing my own repo(emfox/core) but not the official one(devcoin/core), I will change is later.

please check it here, you can check the build log, whatever success or failure, or directly download and use the devcoind image.

https://hub.docker.com/r/emfox/devcoin/

OK yes, of course

Thanks for the promoting

I just upgraded faucet.d.evco.in and block.d.evco.in to https, and remade some ui code, anyone please test if they work properly.

and I've moved the site to another machine, so the faucet.devcoin.org and blockchain.devcoin.org has wrong redirection, please could the admin of devcoin.org help to do CNAME records instead of A records?

My seed node is running at d.evco.in and default port

remove dvc.rpwt.org and devcoin.rpwt.org, change to d.evco.in

Where's the new version?

Me too. but truely, If we want to follow bitcoin, we should consider using autotools, that bitcoin has already did in 0.8.6 (or may be 0.8.7?)

Hello wolf. As the current linux admin of devcoin, I tell you just go ahead, to adapt the build method of linux as you like, and ask sidhujag to pull it. Because he is of the responsibility of developing our new release, but not the release manager of every distribution (though he happened to be maintaining the windows build). I was not too familiar with those libcurl hacks, and a little too busy to dig into it, so just modify the code (of linux part) as you like. I think sidhujag would like to see it, too, right?

10K dvc is on the way.

Please do it, and give the code (method) so others could repeat your work.

If sidhujag didn't change something recently, you could use my node at 'd.evco.in', using default port.

Let's start disscussing in coinzen.org !

@sidhujag, please refer to http://coinzen.org/index.php/topic,148.msg2354.html#msg2354

please post your step of compiling, and the exact error message.

dvccountdown read my d.evco.in/charity log, which read github/Unthinkingbit/charity, so it mean Unthinkingbit has not already update github record to the newest version, so this cause the inconsistance.

ok, I admit sometimes I may be missing some questions not linux concerned, it should be my fault if I know the answer but not answering it.

Talking to the wallet maintaince. I think I have expressed my meaning and plan of linux version, let me say it in detail again here:
1. people using devcoind more often than devcoin-qt (gui version, I mean) in linux environment
2. those who using devcoind is mostly would like to build devcoind themself rather than using pre-built binarys, so it not urgent to redistribute binary version for linux
3. I haven't find suitable and graceful way of building linux version of devcoin-qt, and concerning both the static and dynamic link method, though I've built an ugly one, but no one seems have test it.
4. the current makefile manual hack cause some issue (like you should wipe */.deps first before doing linux build), and I'd like to use automake/autoconf building system that bitcoin 0.8.6 already use, which is beatiful and os independent, but I heard you'd like to wait till 0.8.5 of devcoin became stable and matual before we move forward, so I'm still thinking I should wait or port it myself first ...

and last, a little busy myself recently, so I haven't rebuild any new version of linux wallet.  but I do actively testing the wallet, I've used 1.0.7 1.0.9 1.0.13 1.0.14 1.0.15, and redistributed some version (1.0.13 or .9?) to my friend, encourage them to use and testing our shinning new wallet. some of them lost 250,000 devcoins due to the fee issue, I just covered this myself because I realised it's a kind of support to devcoin development while the one who lost his coins didn't think so.

Edit: I found the reply I post https://bitcointalk.org/index.php?topic=233997.msg4613062#msg4613062 , that was exactly me and only built the linux test version.

It's really serious accusation, and let me clarify it.

My admin job is Linux wallet maintainance and help people install on their own linux box. since it's now we actively developing and testing new wallet (and I think I do did something during this phase), I haven't starting packaging an new official one( and have done an testing one, but now no one tested or give me feedbacks).

concerning helping people compiling or installed devcoin wallet in their linux box, there is not much questions there(this forum thread) , and I've answered all those who have posted or directly send pms to me (maybe Hunterbunter can prove it that he has contacted me about devcoind compiling, or installation I don't remember well).

So, I am working as an admin.


Edit: Yes, I confirmed it's Hunterbunter who've contacted me, and also recently question I've answered in this thread https://bitcointalk.org/index.php?topic=233997.msg4355754#msg4355754 . too long this thread is, I woundn't like to dig the whole thread again to find more.