I think we broke it already, doh. edit: its back  yeah, i'm still tweaking some things, so it might go down for a few seconds/minutes sometimes |
|
|
|
|
I just managed to get Abe (a block explorer) to work with Yacoin. Dunno if everything works as it should, but so far it looks good. I'll try to polish it and then set it up on amazon cloud or something and publish the source.
|
|
|
|
static const int MAX_OUTBOUND_CONNECTIONS = 8; is old code and should really be changed for all forks.
yeah, I'm behind an overly-restrictive firewall, so I do this to all coins I use. |
|
|
|
Tonight I hope to get the blockchain explorer up and running, as this feels like something we really need working now for the long-term credibility of YAC.
^ this. |
|
|
|
First, kudos for your initiave. * Code sign Windows binaries to prevent modification? This kinda screws anonymity though. If I use my own Verisign code-signing keys, just about everyone knows who I am IRL.
You can sign the binaries with a GPG key dedicated to this project and let some other trusted community members sign this keypair with their own GPG keys, thus making a web of trust around this project. Anonymity preserved, possible signature revocation should the private key ever get compromised, etc. |
|
|
|
"We give away 0.001 Yacoins to each unique visitor."...  Not a single person other than me donated to the faucet and all the YACs I sent are gone. The giveaway was at 0.1 a long time. Better add ReCAPTCHA than Facebook login. Not everyone have Facebook account or are willing to make one to get some YAC from faucet, you know?
Yeah, so someone would just change IP, generate new address and solve a captcha... Really? |
|
|
|
Yet Another cryptocoin that does not address the main problem of bitcoin: the recentralization via pools.
A lot of effort to discourage GPUs and ASICs, but pools are still an option.
Bad, bad, bad...
I don't see any problem with pools, especially if it's p2pool. |
|
|
|
I guess it just takes its time to propagate to all FB servers... |
|
|
|
Get your free Yacoins today! http://yac-faucet.tkFaucet runs on donations: Y5EeQjyhPC6DUZp5rzKVKGQRXyrpxunAz7 |
|
|
|
Yet Another Yet Another Coin Faucet http://yac-faucet.tk/Help spread the love: Y5EeQjyhPC6DUZp5rzKVKGQRXyrpxunAz7 |
|
|
|
@sairon
I can build the yac_scrypt module now, but i still bump into the error you mentioned.
Yeah, I've successfully built it, although with environment variable for the compile flags, so that's why it isn't in the repo. So far the P2Pool managed only once to connect to yacoind (out of a million tries, duh -.-") and it failed anyway... Right now I'm trying to get a blockexplorer for YAC online, so I'll stay away from this for a while. |
|
|
|
AWESOME. I need to rush to the mall to replace a fried power brick. Will start playing with it in a bit.
LOL I rebuilt yacoind and it started working.  Now I get failures when receiving block headers. |
|
|
|
I'm trying to get P2Pool working. Network spec seems to be OK, however I can't get it to connect to yacoind via P2P port (RPC works fine as far as I can tell). $ python2.7 run_p2pool.py --net yacoin
2013-05-11 02:05:35.471844 p2pool (version 11.4-2-g46576ea)
2013-05-11 02:05:35.471956
2013-05-11 02:05:35.472062 Testing bitcoind RPC connection to 'http://127.0.0.1:9323/' with username 'yacoin'...
2013-05-11 02:05:35.483656 ...success!
2013-05-11 02:05:35.483760 Current block hash: 42165354bd7b7bfc9a0c0dda6d6a741df887b127b425512e85f0ba34
2013-05-11 02:05:35.483823 Current block height: 49268
2013-05-11 02:05:35.483871
2013-05-11 02:05:35.483932 Testing bitcoind P2P connection to '127.0.0.1:7688'...
...and here it stays.  |
|
|
|
|
Show Posts
