Topic: [ANN][YAC] YACoin ongoing development - page 71. (Read 380060 times)

I'm seeing about half of my regular mining speed on my CPU miners.  Are you getting about half of your N = 14 hashrate with your GPUs?

Network difficulty is still set to the old N (0.017). According to coinmine.pl there will be 24hours before the difficulty drop (to 0.01).

I notice that after N change the CPU miner (minerd-yacoin-stratum on 5 Xeon cores) isn't getting much slower in term of hash rate but my laptop GPU (GT640M running on cudaminer) gets to 1/3 of N14 hash rate. Now these CPU and GPU miners run at about the same hash rate. YAC is a CPU coin again 
I have to stop my bigger NVdia GPU because it's getting 90C ! Probably due to summer, not the new N.

Try same settings, but lookup-gap x2 bigger

ivanlabrie is the man for this! He may be sleeping right now though.

Any api on that explorer? Official one is giving me errors.

WindMaster needs to update the OP! Add the cryptoaltex and groko's block explorer.

Any idea for the new config for 750ti using cudaminer for the new nfactor?

would be nice to know thanks!

The difficulty is too damn high! At least the pump and dumpers will leave us for a while.

Just a little over 30 minutes before NFactor of 15 becomes our new life for the next few months!

Who's as excited as I am?  

EDIT: Woohoo, it's here!  Miners adapted and no hiccups

That is really fast. I wasn't aware about this explorer. Tnx.
Besides I have been getting a lot of errors lately with explorer.yacoin.org (python script, class 'psycopg2.DataError...).

I just check this out.  It is really fast.  It's even quicker then trying to find a transaction through my YAC qt wallet!

Thanks Ron! I'm glad you appreciate my simple HTML approach. My web page design skills
are a bit for wanting that is for sure. And I have never attempted to do anything using
JavaScript. But I'm planning on skipping that skill-set with Ruby Rails. My yacoin forum is
a Ruby Rails application.

As far as my data goes, it looks like you guessed it. My data is coming from a live
yacoind executable in server mode that I query using a yacoind executable in client mode
doing RPC calls to the server. It's pretty simple really. But g-damn it's fast. I added
address balance tracking that keeps up to the minute with every new block and responds to
a block chain reorganize. I have a new top 1000 list of addresses that is also kept up to
date on the fly. Check it out here: http://explore.grokonet.com/?top1000=1

nah, leveldb is cool, the problem is it just seems wrong to store the same data twice. either way, i use it from python, not c/c++

but did the speaker survive?

Hi Sairon

levelDB shouldn't phase you.  Have you seen my video on building a static leveldb library, at
https://www.youtube.com/watch?v=x1U1cBx6Ub0?  Should be easy to port back to gcc.  Bitcoin has been doing it since ~0.8.0  YACoins data only seems to be about 300MB / year?

And do you know what a famous pundit said about scriptaculous & other javascript "frameworks"?  I was at a NFJS conference and the (anonymous speaker) said they appear to him to be a "steaming pile of code"

Ron

I've done something similar with my prototype explorer, though it's using websockets instead of polling the server every x seconds, which is imo cool. The browser support still sucks, however (and my html&js skills, too, for that matter - guess i'll just focus on finishing the damn electrum client finally in my next coding session).

it sure looks nice, but adapting it for yac seems kinda challenging given most things are hardcoded in multiple places. also, i don't like the prospect of running Yet Another leveldb alongside the electrum's with essentially the same data. (and neither do i like node.js )

 Hi Groko

It's nice to see someone who can still write HTML   One can easily add a "smidge" of Javascript to that html that would "ask" for a new block every ~30 seconds or ~minute or what ever time period you like.  It could even be "done with AJAX". 

Where is the server getting its data from, might I ask?  Is it an "ABE" YACoin talking to a yacoin daemon on the server?

Ron

Those are really useful features no one focuses on...they just assume bitcoind works 100%.
Thanks and props!

+1,  (lol)

but on another note, I have some additions to the UI experience, not the underlying workings of YACoin.  It is too late ATM tonight to do battle with GitHub, but here are some of the additions I have done and tested on the Windows (gcc and MSVC++) builds of YACoind and the gcc YACoin-qt.

http://youtu.be/C8GvHpjbAnM
YACoin is also mentioned in the end of the last of the short video series I did on building static libraries for MSVS, Bitcoin and YACoin and others, see (from message # 2119)
https://www.youtube.com/playlist?list=PLFnWb0ttBBMLyUuniLp3PJ5Mn4tVUlliZ

What's not shown is one more addition to the code, to enable wallet.dat to change its name, to anything!  And to be anywhere on your computer.  I don't have a video, but it would cover something like this:

In YACoin.conf (or on the command line) for Windows (#ifdef WIN32) versions of YACoind (MS), YACoind (gcc) & YACoin-qt (gcc) there is a new optional walletpath argument.  I don't have Linux or a Mac, so I can't test it on other OS's.  That is why I "guarded" it with the WIN32 test, but it should work with any OS.

walletpath can take a full or partial path (or just a filename) to an existing 'wallet.dat' file or a non-existing name to create a new wallet with that new name.  If it's a partial path or just a name, the code 'falls back' to using 'datadir' to compose the full path, which is what the normal code does anyway.

The 'wallet.dat' name can be any legal filename!

One thing one can do with this capability is run the wallet off of a USB memory drive and never have it on the hard drive of the computer!

Change wallets by editing a line in YACoin.conf, without losing the other wallet, which is the same as running the same blockchain with different wallets.

Perhaps an odd use of running the same wallet on different blockchains?

All one needs to know is how the BerkeleyDB code is written in Bitcoin/YACoin, etc.

In YACoin, the wallet code expects a blkindex.dat and (possibly) a  database/log.0000000nnn file in the directory with the wallet file, 'wallet.dat' or whatever you want to rename it!

The blockchain, I think, is in the 'datadir' directory, wherever that is on your computer, and it expects to find a blk0001.dat and perhaps a peers.dat and the ability to have a .lock file.

There is some connection, I believe, but again there is no documentation, on the relationship between the 'datadir'/blk001.dat file and the blkindex.dat and (possibly) a database/log.0000000nnn files in the walletpath which now can be a separate directory!

Perhaps YACoin can soon (?) have multiple wallets on one block chain?  Built in!  Without an RPC connection?  Or with one?  Can you see an "exchange" kind of application?  Or other possibilities?

Is there any interest in these additions?  I have found it very useful for testing as a developer and as a user, and have been using this code on my Bitcoin MSVC++ and gcc versions for some time

Ron

YAC: Y3ZggXDvnRJaRwtVGyGJwt6DMLN3EPQpQf

I know one person with a Mac, my retired father - I can't picture that ending well... I was honestly happy the day he got a Mac - it meant an end to being tech support for him!

Has anyone been able to verify/test the Mac wallet?