Roister01
|
|
December 24, 2016, 05:36:21 PM |
|
yes Ron, I had read that, and have put the wallet file in the extracted yacoindata directory folder..I can se it in there, but there is also a file that says wallet.dat, not my file. Do I need to delete this one?
I still have the 0.4.4 version on my laptop though, which still opens up with the original data file in it. Do I need to delete all this before the new one will recognise the wallet file in the new directory? I do struggle with this sort of stuff!
Many thanks,
Roister01
|
|
|
|
|
|
|
|
|
Whoever mines the block which ends up containing your transaction will get its fee.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
old c coder
|
|
December 24, 2016, 06:14:35 PM |
|
yes Ron, I had read that, and have put the wallet file in the extracted yacoindata directory folder..I can se it in there, but there is also a file that says wallet.dat, not my file. Do I need to delete this one?
I still have the 0.4.4 version on my laptop though, which still opens up with the original data file in it. Do I need to delete all this before the new one will recognise the wallet file in the new directory? I do struggle with this sort of stuff!
Many thanks,
Roister01
Hello Roister01, In the zip file, there is only a file called 'wallet empty.dat', AFAIK!? So what are you referring to? Are you sure you read the readme.txt? Quoting it out of context again The intent of this collection of files is that after one decides where to use them, on a USB drive, external or internal hard drives, etc., one launches the daemon by double clicking or running yD.bat for the daemon or y.bat for the MS daemon, or yQt.bat for the gui.
Hint: you may (should) look at those batch files to see and understand what they do! Ron
|
LTC: LUYiMVsrFQewUSPDasSKGzhyTPAkiTeSov BTC: 1DPvP6WoZzaNQ9Nxzd64hjYad1kyQzTTbx YAC: Y3ZggXDvnRJaRwtVGyGJwt6DMLN3EPQpQf The day is coming when a single carrot, freshly observed, will set off a revolution. Paul Cezanne
|
|
|
Roister01
|
|
December 24, 2016, 06:25:40 PM Last edit: December 24, 2016, 06:53:49 PM by Roister01 |
|
No worries...yes, I meant wallet empty.dat. The 0.4.4 is working fine at the moment...I think Alenevaa helped me set that up. I don't really understand how these things work, was just trying to help the coin work better...i'll leave it to you experts... Cheers, Roister...
|
|
|
|
old c coder
|
|
December 24, 2016, 11:07:50 PM |
|
No worries...yes, I meant wallet empty.dat. The 0.4.4 is working fine at the moment...I think Alenevaa helped me set that up. I don't really understand how these things work, was just trying to help the coin work better...i'll leave it to you experts... Cheers, Roister... Hello Roister, This ain't rocket science Are you familiar with DOS before Windows? CPM before DOS? Linux/unix command lines? It's all basically the same thing!! A CPU is given a set of instructions (usually) in its native machine language which is essentially just a series of numbers. This is called the program, and is usually stored as a file with a file name, in a directory, on some kind of disk or USB drive. In Windows these files are called executable programs, given the file extension '.exe'. Other OSs (operating systems) may/probably use different file extensions? Notice that there are .exe files in the .zip collection called yacoind.exe and yac046.exe. Those are the daemon versions of the Yacoin program. The program Yacoin-qt.exe is the GUI (graphical user interface) version. Now programs are tailored to the particular machine, OS, etc. they are installed on, sometimes by an installation program, an example of which is InstallShield. There are others. The latest versions of Windows (Vista, 7, 8, 8.1, 10) are "picky' about what 'rights' programs have depending upon where they are on your hard disk drive (what directory), and even where you can copy them to on your hard drive! If you have administrative right as the 'user' of your Windows machine, Windows is less 'picky' about what you can or cannot do! So are you an 'administrater' on your Windows machine? Are you the master of your domain? Oops that's from Seinfeld The batch files, with the extension .bat (short for batch), are just text files that are a series of one or more commands to the OS, one per line, and each command is usually just the name of the program that should be run by the OS. Yacoin and all the other bitcoin clones/derivatives are just variations of one incarnation (version) of bitcoin or another. They all are configurable at the moment they are launched, by giving the program an argument which is the name of a configuration file (which is just text!) when it is 'invoked' by just naming it on the 'command line'. The batch files I provide, (again did you read the reame.txt?), 'invoke' the appropriate Yacoin program with an appropriate configuration (text) file and tell the yacoin program where the block chain (that is provided in the YAcoinDataDirectory) is located. This is so that the program uses the faster leveldb block chain data as opposed to your yacoin 0.4.4 slower BerkeleyDB blockchain data. I claim, by testing, that the statements in the readme.txt file are true, i.e. You may copy this branch (.../test*.*) to anywhere on your system, that you have write privileges! .../users/whatever/... would be OK and everything would work from there too. You could even run it off of a USB memory/drive stick!
You can copy the files to your normal locations and work from there. These last three emails are basically all succintly stated in that readme.txt file. You should be able to run the new version or your old version easily, given this information. Just not at the same time Has anyone else reading this tried it out? Successfully? Questions, commentz, tips Ron
|
LTC: LUYiMVsrFQewUSPDasSKGzhyTPAkiTeSov BTC: 1DPvP6WoZzaNQ9Nxzd64hjYad1kyQzTTbx YAC: Y3ZggXDvnRJaRwtVGyGJwt6DMLN3EPQpQf The day is coming when a single carrot, freshly observed, will set off a revolution. Paul Cezanne
|
|
|
Beave162
|
|
December 25, 2016, 05:46:10 AM |
|
yes Ron, I had read that, and have put the wallet file in the extracted yacoindata directory folder..I can se it in there, but there is also a file that says wallet.dat, not my file. Do I need to delete this one?
I still have the 0.4.4 version on my laptop though, which still opens up with the original data file in it. Do I need to delete all this before the new one will recognise the wallet file in the new directory? I do struggle with this sort of stuff!
Many thanks,
Roister01
To answer you briefly, yes, just copy your wallet.dat into the YAcoinDataDirectory. You can ignore the "wallet empty.dat" Double click on the yQt to run the Qt. I suggest you don't try to run multiple instances of it. Mine is minting, and it was very quick to load! It is a great improvement over 0.4.4!
|
YaCoin: YL5kf54wPPXKsXd5T18xCaNkyUsS1DgY7z BitCoin: 14PFbLyUdTyxZg3V8hnvj5VXkx3dhthmDj
|
|
|
Roister01
|
|
December 26, 2016, 10:11:25 AM |
|
Wow..thanks very much for the computer lesson there Ron...you obviously know your stuff! My problem is that when I was at school, the only two computers we had were in a locked room, accessible to very few folk...I never really recovered from that, though I think they are fantastic when they are set up to do what i want them to... I did have a vic20 for a few years, where i vaguely remember typing in something like 10 print "?" 20 goto 10 30 run but that was, and still is my sum knowledge of programming! Thanks very much for your time though, bet it is great to understand all that stuff... I really had read your readme info...though, there is a difference between reading and understanding. I have now got it to work on the new version though. The problem could have been that I saved my backup data under a different name, eg date.dat, the day that I backed up the info, and I was trying to add this file to the directory folder...could this be why it wasn't working? I only wonder, because as a matter of interest, I renamed the file wallet.dat, and hey presto, it started to work! May just be coincidence, but anyway, another node for the network now... Thanks again Ron, and Ben for your help too... Roister...
|
|
|
|
old c coder
|
|
December 26, 2016, 10:04:09 PM |
|
Wow..thanks very much for the computer lesson there Ron...you obviously know your stuff! My problem is that when I was at school, the only two computers we had were in a locked room, accessible to very few folk...I never really recovered from that, though I think they are fantastic when they are set up to do what i want them to... I did have a vic20 for a few years, where i vaguely remember typing in something like 10 print "?" 20 goto 10 30 run but that was, and still is my sum knowledge of programming! Thanks very much for your time though, bet it is great to understand all that stuff... I really had read your readme info...though, there is a difference between reading and understanding. I have now got it to work on the new version though. The problem could have been that I saved my backup data under a different name, eg date.dat, the day that I backed up the info, and I was trying to add this file to the directory folder...could this be why it wasn't working? I only wonder, because as a matter of interest, I renamed the file wallet.dat, and hey presto, it started to work! May just be coincidence, but anyway, another node for the network now... Thanks again Ron, and Ben for your help too... Roister... Hello Roister, When i went to college, there were no micro processors! Barely mini computers If you didn't understand something in the readme.txt file when you read it, just ask the question! That is what this forum is or should be about! There are no stupid/foolish questions, but plenty of stupid/foolish answers! As to a wallet.dat named (some)dat.dat, that's fine, actually a good idea. The idea to have one's *coin program load (start up) with wallet.dat(s) named anything, goes back to 7/2/2013! See https://bitcointalk.org/index.php?topic=149479.msg3214374#msg3214374 which refers to https://github.com/old-c-coder/bitcoin-git/commit/929019012dc7d93fd3ba59d8eb553e390211a713Now bitcoin finally got around to that idea, many versions later, since I now see it in 0.13.0!! Of course I got no credit So to your question. You can keep your wallet.dat called 'date.dat' and just tell yacoin in its configuration file YACoin045.conf by adding a line such as: wallet = date.datRon
|
LTC: LUYiMVsrFQewUSPDasSKGzhyTPAkiTeSov BTC: 1DPvP6WoZzaNQ9Nxzd64hjYad1kyQzTTbx YAC: Y3ZggXDvnRJaRwtVGyGJwt6DMLN3EPQpQf The day is coming when a single carrot, freshly observed, will set off a revolution. Paul Cezanne
|
|
|
Joe_Bauers
|
|
December 27, 2016, 09:01:26 PM |
|
old c coder :: Did you find a solution yet to the 14+ day import of bootstrap.dat? That is what I'm working on, and would say should be the #1 priority.
|
|
|
|
Beave162
|
|
December 28, 2016, 04:49:00 AM |
|
old c coder :: Did you find a solution yet to the 14+ day import of bootstrap.dat? That is what I'm working on, and would say should be the #1 priority.
It takes no time at all to load!
|
YaCoin: YL5kf54wPPXKsXd5T18xCaNkyUsS1DgY7z BitCoin: 14PFbLyUdTyxZg3V8hnvj5VXkx3dhthmDj
|
|
|
Joe_Bauers
|
|
December 28, 2016, 06:13:17 AM |
|
old c coder :: Did you find a solution yet to the 14+ day import of bootstrap.dat? That is what I'm working on, and would say should be the #1 priority.
It takes no time at all to load! This: https://github.com/ya4-old-c-coder/yacoinis basically a year behind this: https://github.com/yacoin/yacoin/tree/testing which is the "ready to go" official 0.4.5 code. Do a compare to see the thousands of differences, including the much better network code. The only problem is that due to scrypt-jane doing it's job, at higher N values it becomes very slow to import a bootstrap.dat file. There is no optimal solution to fix this that I've found, outside of removing all block checks for a bootstrap import, or including an entire Yacoin data directory, which is what I'm guessing Ron has done in yac048boot.zip? Either way removes the *mostly trustless nature of YAC. *Mostly, due to checkpoints still being a thing, but avoids someone having to download the entire block-chain from scratch so it's a trade-off. I'm pretty tired beating a dead horse on all of this, so if Ron wants to continue to do his own thing using an old code base and can also get his version to work on Linux, and preferably Mac as well, then go for it and I will merge that to https://github.com/yacoin/yacoin/tree/master assuming it's better than current 0.4.4 code.
|
|
|
|
devlin
|
|
December 28, 2016, 07:00:37 AM |
|
I think high N factor is and will be a problem for YAC network, as far as i know other scrypt-jane coins change to static N or POS. In aug.2017 N factor will be 19. Is hard to maintain a healthy network at higher N.
|
|
|
|
Beave162
|
|
December 28, 2016, 08:31:00 AM |
|
There is no optimal solution to fix this that I've found, outside of removing all block checks for a bootstrap import, or including an entire Yacoin data directory, which is what I'm guessing Ron has done in yac048boot.zip? Either way removes the *mostly trustless nature of YAC. *Mostly, due to checkpoints still being a thing, but avoids someone having to download the entire block-chain from scratch so it's a trade-off.
That is what Ron has done. You should really check it out. There is a legitimate point to be had in regards to how NFactor increases jeopardize the network--in addition to the bootstrap problem. The original idea behind the NFactor increases was to maintain asic-resistance and recruit more players and stakeholders as CPUs gain more and more of competitive advantage over GPUs. The intent has not been served. It is time for YAC to consider a freeze at current NF or revert to NF16.
|
YaCoin: YL5kf54wPPXKsXd5T18xCaNkyUsS1DgY7z BitCoin: 14PFbLyUdTyxZg3V8hnvj5VXkx3dhthmDj
|
|
|
Beave162
|
|
January 08, 2017, 10:58:19 PM |
|
YAC has finally been delisted from BTER!
Now, YAC no longer has to be associated with those criminals at BTER, who will steal your coins without batting an eye.
|
YaCoin: YL5kf54wPPXKsXd5T18xCaNkyUsS1DgY7z BitCoin: 14PFbLyUdTyxZg3V8hnvj5VXkx3dhthmDj
|
|
|
yusyus
|
|
January 20, 2017, 06:39:07 PM |
|
I like this coin. I am buying on Yobit. And when new wallet will be releised? Anybody know?
|
|
|
|
Roister01
|
|
January 21, 2017, 10:15:56 PM |
|
I thought I read that someone was buying this on yobit! Looks more like selling to me...😐
|
|
|
|
logictense
|
|
January 21, 2017, 10:54:17 PM |
|
I thought I read that someone was buying this on yobit! Looks more like selling to me...😐
Right, selling pressure is stronger than ever. Remember, I suggested u to exit yac, but u ignored my advice and took a loss.
|
|
|
|
Beave162
|
|
January 21, 2017, 11:45:39 PM |
|
I thought I read that someone was buying this on yobit! Looks more like selling to me...😐
Two fundamentals of YACoin (and all the other clones) that have proven not to work: NFactor increases; PoS-PoW hybrid system. It would certainly not hurt to get input from anyone and everyone who still follows this thread.
|
YaCoin: YL5kf54wPPXKsXd5T18xCaNkyUsS1DgY7z BitCoin: 14PFbLyUdTyxZg3V8hnvj5VXkx3dhthmDj
|
|
|
Beave162
|
|
January 29, 2017, 09:51:27 PM |
|
yacoin.org is down at the moment.
Bad news... YAC is in need of developers.
|
YaCoin: YL5kf54wPPXKsXd5T18xCaNkyUsS1DgY7z BitCoin: 14PFbLyUdTyxZg3V8hnvj5VXkx3dhthmDj
|
|
|
Joe_Bauers
|
|
January 30, 2017, 09:45:27 PM |
|
yacoin.org is down at the moment.
Bad news... YAC is in need of developers.
Site will be down until hosting transfer. I thought old c coder was taking his ideas forward?
|
|
|
|
Roister01
|
|
February 01, 2017, 10:59:11 PM |
|
Blimey...what's up with yac.. a price rise!
|
|
|
|
|