anyone got a list of addnodes for the conf file? i can't get any connections on the windows qt
Many thanks
Fuzzybear
Topic: [ANN][YAC] YACoin ongoing development - page 43. (Read 379983 times)
Cross-posting this here:
What I don't get, is that if I'm mining at Nfactor 15, N is 65536. Why does rawintensity 7168 NOT work with a buffer-size of 3800 at lookup-gap 16?
One block is 128 bytes. 128 * 65536 / 16 = 524288 bytes per thread.
524288 bytes / 1024 / 1024 = .5MiB.
.5MiB fits into 3800MiB 7600 times: 3800 / .5 = 7600.
Therefore, max rawintensity without hardware errors SHOULD be 7600...
This works with my 280X - 290X, nope.
What I don't get, is that if I'm mining at Nfactor 15, N is 65536. Why does rawintensity 7168 NOT work with a buffer-size of 3800 at lookup-gap 16?
One block is 128 bytes. 128 * 65536 / 16 = 524288 bytes per thread.
524288 bytes / 1024 / 1024 = .5MiB.
.5MiB fits into 3800MiB 7600 times: 3800 / .5 = 7600.
Therefore, max rawintensity without hardware errors SHOULD be 7600...
This works with my 280X - 290X, nope.
I've had the same mysterious issues with yacoin mining before...Thirtybird should know more.
I couldn't figure it out on the 290s, but 280x and older (or cheaper gpus) did work.
Yes, and 13.12 can't generate code for shit.
I was reminded of the above quote today. Do you think that Yacoin continues some of the original bitcoin ideals?
In case some of the devs that help out aren't subscribed to the githib feed,
I released the new testing version yesterday.
1) The first thing that needs to be looked at is GetBlockTrust() in main. I "eyeballed" the changes but it needs to be thourougly debugged.
2) Someone with some extra resources needs to hash out a proper testnet that will make things like the above a bit more efficient
3) Update the Novacoin MSVC solution for Yacoin.
I do have a compiled Windows version, but I don't want to release it generally unless you can help on the dev side.
P.S.
Don't forget to back up your yacoin data folder before testing!
I released the new testing version yesterday.
1) The first thing that needs to be looked at is GetBlockTrust() in main. I "eyeballed" the changes but it needs to be thourougly debugged.
2) Someone with some extra resources needs to hash out a proper testnet that will make things like the above a bit more efficient
3) Update the Novacoin MSVC solution for Yacoin.
I do have a compiled Windows version, but I don't want to release it generally unless you can help on the dev side.
P.S.
Don't forget to back up your yacoin data folder before testing!
That is great job, Joe.
I don't have time to test it yet, but I will get to it asap. I did checked GetBlockTrust() and it doesn't look more harmful than current implementation
Anyway thumbs up ...
In case some of the devs that help out aren't subscribed to the githib feed,
I released the new testing version yesterday.
1) The first thing that needs to be looked at is GetBlockTrust() in main. I "eyeballed" the changes but it needs to be thourougly debugged.
2) Someone with some extra resources needs to hash out a proper testnet that will make things like the above a bit more efficient
3) Update the Novacoin MSVC solution for Yacoin.
I do have a compiled Windows version, but I don't want to release it generally unless you can help on the dev side.
P.S.
Don't forget to back up your yacoin data folder before testing!
I released the new testing version yesterday.
1) The first thing that needs to be looked at is GetBlockTrust() in main. I "eyeballed" the changes but it needs to be thourougly debugged.
2) Someone with some extra resources needs to hash out a proper testnet that will make things like the above a bit more efficient
3) Update the Novacoin MSVC solution for Yacoin.
I do have a compiled Windows version, but I don't want to release it generally unless you can help on the dev side.
P.S.
Don't forget to back up your yacoin data folder before testing!
Sounds good senj.
Just a quick update. I've been sick for the past few days, so I'm a bit behind schedule. Feeling better today, so I am planning on releasing the test version within 3 or 4 days.
Just a quick update. I've been sick for the past few days, so I'm a bit behind schedule. Feeling better today, so I am planning on releasing the test version within 3 or 4 days.
Don't work too hard if you had the flu. There is a bad one around that's resistant to the flu jab so everyone's getting it.
Sounds good senj.
Just a quick update. I've been sick for the past few days, so I'm a bit behind schedule. Feeling better today, so I am planning on releasing the test version within 3 or 4 days.
Just a quick update. I've been sick for the past few days, so I'm a bit behind schedule. Feeling better today, so I am planning on releasing the test version within 3 or 4 days.
...
In the new version of bitcoin core qt (v10) there were some improvements to loading / downloading the blockchain by making usage of 'block headers'. It sounded like wallet is now able to view a small part of the downloaded block chain to 'check' that it is correct. I'm wondering if there would be someway to do that senj's pre-loaded blockchain file. That way we would have quicker boot time with out any security risks.
In the new version of bitcoin core qt (v10) there were some improvements to loading / downloading the blockchain by making usage of 'block headers'. It sounded like wallet is now able to view a small part of the downloaded block chain to 'check' that it is correct. I'm wondering if there would be someway to do that senj's pre-loaded blockchain file. That way we would have quicker boot time with out any security risks.
I think this is planned to speed up client chain download (first headers, later transactions - possibly on demand) and enable "thinner" clients with less disk space requirements. This is not yet in a version Joe is working on now - so I believe.
...
Great to hear. Once I upload testing to github, we can see about merging this for 0.4.5.
Reindex works fine in 0.4.5, and I am also going to include a bootstrap file which takes a few hours to import. As you mentioned, everyone will need to do this, or wait 3 days to sync from network peers
Great to hear. Once I upload testing to github, we can see about merging this for 0.4.5.
Reindex works fine in 0.4.5, and I am also going to include a bootstrap file which takes a few hours to import. As you mentioned, everyone will need to do this, or wait 3 days to sync from network peers
I am not sure what kind of merging do you have in mind, I am using wxWidgets C++ framework (without gui components) for this tool.
Code is not ment to be merged with yacoin. But I will publish it after I clean it a bit more. Besides I plan to either extend functionality later or create separate tools.
I am looking forward to reindex:)
Cross-posting this here:
What I don't get, is that if I'm mining at Nfactor 15, N is 65536. Why does rawintensity 7168 NOT work with a buffer-size of 3800 at lookup-gap 16?
One block is 128 bytes. 128 * 65536 / 16 = 524288 bytes per thread.
524288 bytes / 1024 / 1024 = .5MiB.
.5MiB fits into 3800MiB 7600 times: 3800 / .5 = 7600.
Therefore, max rawintensity without hardware errors SHOULD be 7600...
This works with my 280X - 290X, nope.
What I don't get, is that if I'm mining at Nfactor 15, N is 65536. Why does rawintensity 7168 NOT work with a buffer-size of 3800 at lookup-gap 16?
One block is 128 bytes. 128 * 65536 / 16 = 524288 bytes per thread.
524288 bytes / 1024 / 1024 = .5MiB.
.5MiB fits into 3800MiB 7600 times: 3800 / .5 = 7600.
Therefore, max rawintensity without hardware errors SHOULD be 7600...
This works with my 280X - 290X, nope.
That is great news Joe.
I developed a tool for fast blockchain file sorting -> backing up. I was thinking of also putting online sorted *.dat files for first 1M blocks (and later perhaps every icremental 100 or 200K rows).
I did not know reindex was unavaiable in yacoin. That means all blocks need to be imported again (yacoind -loadblock="sorted.dat") and that is not too much faster than downloading them from peers. On the other hand, the later is a safer option from the point of security.
Does that (reindex option) change in 0.4.5?
My tool was ment to be experimental feature for fast development setups. And for blockchain backups. I thought we need a way to "boot" peers faster, so people do not wait days before thay can even test yacoin
I developed a tool for fast blockchain file sorting -> backing up. I was thinking of also putting online sorted *.dat files for first 1M blocks (and later perhaps every icremental 100 or 200K rows).
I did not know reindex was unavaiable in yacoin. That means all blocks need to be imported again (yacoind -loadblock="sorted.dat") and that is not too much faster than downloading them from peers. On the other hand, the later is a safer option from the point of security.
Does that (reindex option) change in 0.4.5?
My tool was ment to be experimental feature for fast development setups. And for blockchain backups. I thought we need a way to "boot" peers faster, so people do not wait days before thay can even test yacoin
Great to hear. Once I upload testing to github, we can see about merging this for 0.4.5.
Reindex works fine in 0.4.5, and I am also going to include a bootstrap file which takes a few hours to import. As you mentioned, everyone will need to do this, or wait 3 days to sync from network peers
Cross-posting this here:
What I don't get, is that if I'm mining at Nfactor 15, N is 65536. Why does rawintensity 7168 NOT work with a buffer-size of 3800 at lookup-gap 16?
One block is 128 bytes. 128 * 65536 / 16 = 524288 bytes per thread.
524288 bytes / 1024 / 1024 = .5MiB.
.5MiB fits into 3800MiB 7600 times: 3800 / .5 = 7600.
Therefore, max rawintensity without hardware errors SHOULD be 7600...
This works with my 280X - 290X, nope.
What I don't get, is that if I'm mining at Nfactor 15, N is 65536. Why does rawintensity 7168 NOT work with a buffer-size of 3800 at lookup-gap 16?
One block is 128 bytes. 128 * 65536 / 16 = 524288 bytes per thread.
524288 bytes / 1024 / 1024 = .5MiB.
.5MiB fits into 3800MiB 7600 times: 3800 / .5 = 7600.
Therefore, max rawintensity without hardware errors SHOULD be 7600...
This works with my 280X - 290X, nope.
I've had the same mysterious issues with yacoin mining before...Thirtybird should know more.
I couldn't figure it out on the 290s, but 280x and older (or cheaper gpus) did work.
[Professor]Good news everyone![Farnsworth]
I've had a little extra time over the past week and have completed the changes that I posted a few pages back.
I am going to do a bit more testing on my own and then I will release a testing version for everyone by this weekend. Anyone that can help out with testing, please do.
If everything goes as expected, Yacoin 0.4.5 will be released in early March.
We are also getting close to block 1,000,000. I was thinking of doing a giveaway on twitter or our forum. Does anyone else have any ideas or plans?
I've had a little extra time over the past week and have completed the changes that I posted a few pages back.
I am going to do a bit more testing on my own and then I will release a testing version for everyone by this weekend. Anyone that can help out with testing, please do.
If everything goes as expected, Yacoin 0.4.5 will be released in early March.
We are also getting close to block 1,000,000. I was thinking of doing a giveaway on twitter or our forum. Does anyone else have any ideas or plans?
That is great news Joe.
I developed a tool for fast blockchain file sorting -> backing up. I was thinking of also putting online sorted *.dat files for first 1M blocks (and later perhaps every icremental 100 or 200K rows).
I did not know reindex was unavaiable in yacoin. That means all blocks need to be imported again (yacoind -loadblock="sorted.dat") and that is not too much faster than downloading them from peers. On the other hand, the later is a safer option from the point of security.
Does that (reindex option) change in 0.4.5?
My tool was ment to be experimental feature for fast development setups. And for blockchain backups. I thought we need a way to "boot" peers faster, so people do not wait days before thay can even test yacoin.
In the new version of bitcoin core qt (v10) there were some improvements to loading / downloading the blockchain by making usage of 'block headers'. It sounded like wallet is now able to view a small part of the downloaded block chain to 'check' that it is correct. I'm wondering if there would be someway to do that senj's pre-loaded blockchain file. That way we would have quicker boot time with out any security risks.
[Professor]Good news everyone![Farnsworth]
I've had a little extra time over the past week and have completed the changes that I posted a few pages back.
I am going to do a bit more testing on my own and then I will release a testing version for everyone by this weekend. Anyone that can help out with testing, please do.
If everything goes as expected, Yacoin 0.4.5 will be released in early March.
We are also getting close to block 1,000,000. I was thinking of doing a giveaway on twitter or our forum. Does anyone else have any ideas or plans?
I've had a little extra time over the past week and have completed the changes that I posted a few pages back.
I am going to do a bit more testing on my own and then I will release a testing version for everyone by this weekend. Anyone that can help out with testing, please do.
If everything goes as expected, Yacoin 0.4.5 will be released in early March.
We are also getting close to block 1,000,000. I was thinking of doing a giveaway on twitter or our forum. Does anyone else have any ideas or plans?
That is great news Joe.
I developed a tool for fast blockchain file sorting -> backing up. I was thinking of also putting online sorted *.dat files for first 1M blocks (and later perhaps every icremental 100 or 200K rows).
I did not know reindex was unavaiable in yacoin. That means all blocks need to be imported again (yacoind -loadblock="sorted.dat") and that is not too much faster than downloading them from peers. On the other hand, the later is a safer option from the point of security.
Does that (reindex option) change in 0.4.5?
My tool was ment to be experimental feature for fast development setups. And for blockchain backups. I thought we need a way to "boot" peers faster, so people do not wait days before thay can even test yacoin.
[Professor]Good news everyone![Farnsworth]
I've had a little extra time over the past week and have completed the changes that I posted a few pages back.
I am going to do a bit more testing on my own and then I will release a testing version for everyone by this weekend. Anyone that can help out with testing, please do.
I've had a little extra time over the past week and have completed the changes that I posted a few pages back.
I am going to do a bit more testing on my own and then I will release a testing version for everyone by this weekend. Anyone that can help out with testing, please do.
Looking forward to this.
[Professor]Good news everyone![Farnsworth]
I've had a little extra time over the past week and have completed the changes that I posted a few pages back.
I am going to do a bit more testing on my own and then I will release a testing version for everyone by this weekend. Anyone that can help out with testing, please do.
If everything goes as expected, Yacoin 0.4.5 will be released in early March.
We are also getting close to block 1,000,000. I was thinking of doing a giveaway on twitter or our forum. Does anyone else have any ideas or plans?
I've had a little extra time over the past week and have completed the changes that I posted a few pages back.
I am going to do a bit more testing on my own and then I will release a testing version for everyone by this weekend. Anyone that can help out with testing, please do.
If everything goes as expected, Yacoin 0.4.5 will be released in early March.
We are also getting close to block 1,000,000. I was thinking of doing a giveaway on twitter or our forum. Does anyone else have any ideas or plans?
I was thinking about 'upping the ante' on one of my bounties...
https://forum.yacoin.org/index.php?topic=672.0
[Professor]Good news everyone![Farnsworth]
I've had a little extra time over the past week and have completed the changes that I posted a few pages back.
I am going to do a bit more testing on my own and then I will release a testing version for everyone by this weekend. Anyone that can help out with testing, please do.
If everything goes as expected, Yacoin 0.4.5 will be released in early March.
We are also getting close to block 1,000,000. I was thinking of doing a giveaway on twitter or our forum. Does anyone else have any ideas or plans?
I've had a little extra time over the past week and have completed the changes that I posted a few pages back.
I am going to do a bit more testing on my own and then I will release a testing version for everyone by this weekend. Anyone that can help out with testing, please do.
If everything goes as expected, Yacoin 0.4.5 will be released in early March.
We are also getting close to block 1,000,000. I was thinking of doing a giveaway on twitter or our forum. Does anyone else have any ideas or plans?
Windmaster, could you please add that site to the block explorer list in the OP? Also, probably best to remove http://yac.ltcoin.net/ and http://yac.m-s-t.org/ from the list of pools.
Yep, first post updated.
That's great! For some reason, my google chrome won't let me scroll down. 
Now it should.
YAC is stuck on block 925,585? What is happening?
Bad 'luck'? Or maybe a drop in hash rate?
Looks like we're up to block 925,591 now... Either way, the fact that the difficultly readjusts each block, YAC will continue to maintain itself.
https://coinplorer.com/YAC/Blocks/145c52f755ad40cddad94a98e82009abc98c3e5ba8766ccf9ffc496e71302b54
Not sure what happened! It seems everything is good now.
That's great! For some reason, my google chrome won't let me scroll down.
Windmaster, could you please add that site to the block explorer list in the OP? Also, probably best to remove http://yac.ltcoin.net/ and http://yac.m-s-t.org/ from the list of pools.
YAC is stuck on block 925,585? What is happening?
Bad 'luck'? Or maybe a drop in hash rate?
Looks like we're up to block 925,591 now... Either way, the fact that the difficultly readjusts each block, YAC will continue to maintain itself.
https://coinplorer.com/YAC/Blocks/145c52f755ad40cddad94a98e82009abc98c3e5ba8766ccf9ffc496e71302b54
Jump to: