Just read the whitepaper.
This looks like a huge deal to me.
Turning more hashpower on RVN as I type this.
Topic: [ANN] Ravencoin [RVN] PoW GPU Mining | Asset Transfer Blockchain (Updated ANN) - page 237. (Read 1170617 times)
April 03, 2018, 03:12:07 AM
April 03, 2018, 02:55:31 AM
ded. start over.
"nothing" and "ded. start over" are not very professional words to use though, he could have added the word "OLD" in the thread's name and posted the link to the new thread in his post.That's because he no longer cares about the project and was only a community member. This is exactly why there's an ANN hardfork going on right now.
April 03, 2018, 02:40:34 AM
Hi ! RavenCoin is available on LycheeBit.
Happy mining
Mining RavenCoin with x16r algo :
- Stratum : lycheebit.com:3636
- User : YOUR_RVN_ADDRESS
- Password : c=RVN
LycheeBit info :
- Website : https://www.lycheebit.com/
- Payout : Every hour
- Fee : 1.00 %
Mining software :
- Nvidia ccminer : https://github.com/ocminer/suprminer/releases
- Windows CPUMiner : https://rvn.suprnova.cc/cpuminer-multi-rel1.3.3-x64.7z
- Linux CPUMiner : https://github.com/tpruvot/cpuminer-multi
- Mac CPUMiner : https://gist.github.com/quagliero/90f493f123c7b1ddba5428ba0146329a
Examples of command line :
- CPU Miner : cpuminer.exe -a x16r -o stratum+tcp://lycheebit.com:3636 -u RLysqDqScKYZUbsa8o4TUunJGNdeVgB8hB -p c=RVN
Peers list :
- addnode=35.185.76.181:8767
- addnode=35.231.53.152:8767
- addnode=[2001:0:9d38:6ab8:3456:388d:4755:afcf]:8767
- addnode=[2001:0:5ef5:79fb:cbc:3543:475c:1a11]:8767
- addnode=82.69.65.225:8767
- addnode=[2001:0:9d38:6abd:380e:31b1:2b16:49df]:8767
- addnode=[2001:0:4137:9e76:3c2b:33b5:bcfd:17dc]:8767
- addnode=162.212.156.160:8767
April 03, 2018, 02:10:19 AM
A new thread was created because the old thread creator (Kai) decided he wasn't going to maintain it anymore. He's moving onto new ventures. So since his account is the only one with access to that announcement, this was the best way forward. The old announcement now links here.
I will be updating this thread for the future. At least it's a bit cleaner now since all the miners with issues are over on the old thread
I will be updating this thread for the future. At least it's a bit cleaner now since all the miners with issues are over on the old thread
This still makes no sense.
He hasn't locked the other thread, he hasn't made it public that this is what he is doing and why, he hasn't categorically stated that this is the reason why.
In fact, by doing this, he (and you to a large extent) has made this MORE of a mess than it already is by not doing these things.
#crysx
you know what doesn't make sense? building a closed source miner for 6 months built on top of GPL code and then never hiring anyone to rewrite the gpl code and then sitting on your miner, never releasing it. But hey! that's just my opinion man, just like you have yours.
Well ...
That would be true IF it was GPL code you were talking about and NOT closed source private code.
Which has nothing to do with what we are discussing here - and as a newbie profile, I assume was to just poke in the ribs.
So if it was just your 'opinion' then that is baseless and nothing worth dictating to preach. Base it on facts, and I would establish a rapport and conversation about it. Base it on hearsay and fiction like you obviously have, then I will do the same as I have done now and rebutt only to the extent that you are nothing more than bringer of bad tidings, to do divert the real issue here in THIS thread. You want a REAL cheat when it comes what you have described? Go to the spmod thread and see what you have stated in action CURRENTLY.
We have a ccminer fork internally, and DO optimize it, but never release it. That is abiding by the rules of GPL. You should read the license some day, it's enlightening to say the least.
Nice try as an attack, but a dismal fail.
#crysx
Well ...
It was just a poke in the ribs.
Likewise, it's just your 'opinion' that opening this thread creates MORE of a mess(subjective) and to ascribe any fault or actions of the previous thread owner to this thread is baseless and nothing worth dictating to preach(in your words).
Best of luck with your internal ccminer fork and CWIgm
Nice try as an attack, but a dismal fail.
#under
Reminiscent of a user who is on the forums trolling/posting on another profile that is argumentative in every way he can be.
So this is the 'new' profile you intend on using mate? Good one. Shows the gutless means that you decide to take.
In any case, your attack is moot. OUR code is just that, and we can and will do what we want with it. Period! The GPL code is restricted and governed by the licensing, and 'should' be adhered to buy the rules that govern it. It doesn't always happen that way. Why don't you accuse MicroSoft that their OS is based on opensource software and that they are using it internally, but publishing it also. I'm sure that will go down well.
As for the RVN threads. Notice - THREADS! With an 's'. This is the 'mess' that I am talking about. Unlike the use case where a single thread is used by the current owners/developers/users, multiple threads that are used at the same time on the same subject is messy. This not subjective, but factual. It is EASY for the last owner of the thread to have published that post - then lock thread. Explaining that there is a new thread because I have other projects I am working on. Simple.
You on the other hand, seem prefer to have multiple threads on the SAME subject, so good for you. The general populace are those that really shouldn't be misled this way, and need to be directed by the DEV TEAM who control this project, as to which is the correct method and direction the community should or should not take.
#crysx
Stop chasing boogeymen in shadows that don't exist!
I'm not your nemesis masquerading in a new account, I'm just a person new to bitcointalk.org
I really don't care about your code that much, but man you sure get pretty defensive about it.
I was simply making a metaphor about how personal opinions, exclusively your negative one about THIS thread, can be subjective.
Furthermore you seem to put a lot effort into prescribing the 'correct' method for establishing ANN threads. I understand that it is your opinion that ANNs "need to be directed by the DEV TEAM..." I would counter that centralizing all communications under a single authority is completely counter intuitive to the nature of decentralized blockchains. I am curious where Bitcoin's ANN thread is? link pls? (joking)(because there isn't one single thread owner for bitcoin)
So community communication will get messy sometimes in a truly decentralized project. But this thread is an attempt to clean things up- and your insinuations to the opposite are baseless.
No - not that way at all ...
I have endured way too many issues with arguments over so many things - regardless of whether you give a damn about our code or not. When someone wants to argue and a point, or accuse of doing what Rune Stensland (sp_ in this forum) is doing like you have done so in the first post, then I will ALWAYS get defensive if no such thing has occurred. So regardless of what your intention is/was, you accused us of something we have no intention of allowing to follow through with. That is why I get defensive, and why I continuously seem to defend our stance. Posts like yours make it necessary.
Other than that, opinions are just that, opinions. Metaphor or not (which it clearly was not - it was a false accusation), the fact remains that a single unified thread would cause NO confusion as opposed to multiple threads on the SAME subject matter. Maybe I should say 'active' threads instead of just 'multiple' threads. The 'old' thread is still being used and is current, while this thread is also being used and apparently current.
Why is it that the other one can't have a post to say this is the new thread and have it as the last post with the locking of the thread? Too logical to do?
Anyway, I guess we will be going around in circles with this as you seem to think there was no accusation and merely a metaphor with what you accused us of in the initial reply post, and you still think that it is all subjective here with two threads on the same subject by supposedly the same people.
No worries.
Have a great day!
#crysx
Your accusations about THIS thread "(and you to a large extent) has made this MORE of a mess than it already is by not doing these things" initiated this.
I don't understand why you felt the need to sling salt on this thread. I slung some o' that salt back.
You do ask a valid question though, "Why is it that the other one can't have a post to say this is the new thread and have it as the last post with the locking of the thread? Too logical to do?"
But this valid question should be in the other thread and directed to the thread owner.
So moving forward,
Best of luck in your endeavors - lets get back to the topic of RVN!!
April 03, 2018, 02:08:53 AM
ded. start over.
"nothing" and "ded. start over" are not very professional words to use though, he could have added the word "OLD" in the thread's name and posted the link to the new thread in his post. April 03, 2018, 02:00:14 AM
A new thread was created because the old thread creator (Kai) decided he wasn't going to maintain it anymore. He's moving onto new ventures. So since his account is the only one with access to that announcement, this was the best way forward. The old announcement now links here.
I will be updating this thread for the future. At least it's a bit cleaner now since all the miners with issues are over on the old thread
I will be updating this thread for the future. At least it's a bit cleaner now since all the miners with issues are over on the old thread
This still makes no sense.
He hasn't locked the other thread, he hasn't made it public that this is what he is doing and why, he hasn't categorically stated that this is the reason why.
In fact, by doing this, he (and you to a large extent) has made this MORE of a mess than it already is by not doing these things.
#crysx
you know what doesn't make sense? building a closed source miner for 6 months built on top of GPL code and then never hiring anyone to rewrite the gpl code and then sitting on your miner, never releasing it. But hey! that's just my opinion man, just like you have yours.
Well ...
That would be true IF it was GPL code you were talking about and NOT closed source private code.
Which has nothing to do with what we are discussing here - and as a newbie profile, I assume was to just poke in the ribs.
So if it was just your 'opinion' then that is baseless and nothing worth dictating to preach. Base it on facts, and I would establish a rapport and conversation about it. Base it on hearsay and fiction like you obviously have, then I will do the same as I have done now and rebutt only to the extent that you are nothing more than bringer of bad tidings, to do divert the real issue here in THIS thread. You want a REAL cheat when it comes what you have described? Go to the spmod thread and see what you have stated in action CURRENTLY.
We have a ccminer fork internally, and DO optimize it, but never release it. That is abiding by the rules of GPL. You should read the license some day, it's enlightening to say the least.
Nice try as an attack, but a dismal fail.
#crysx
Well ...
It was just a poke in the ribs.
Likewise, it's just your 'opinion' that opening this thread creates MORE of a mess(subjective) and to ascribe any fault or actions of the previous thread owner to this thread is baseless and nothing worth dictating to preach(in your words).
Best of luck with your internal ccminer fork and CWIgm
Nice try as an attack, but a dismal fail.
#under
Reminiscent of a user who is on the forums trolling/posting on another profile that is argumentative in every way he can be.
So this is the 'new' profile you intend on using mate? Good one. Shows the gutless means that you decide to take.
In any case, your attack is moot. OUR code is just that, and we can and will do what we want with it. Period! The GPL code is restricted and governed by the licensing, and 'should' be adhered to buy the rules that govern it. It doesn't always happen that way. Why don't you accuse MicroSoft that their OS is based on opensource software and that they are using it internally, but publishing it also. I'm sure that will go down well.
As for the RVN threads. Notice - THREADS! With an 's'. This is the 'mess' that I am talking about. Unlike the use case where a single thread is used by the current owners/developers/users, multiple threads that are used at the same time on the same subject is messy. This not subjective, but factual. It is EASY for the last owner of the thread to have published that post - then lock thread. Explaining that there is a new thread because I have other projects I am working on. Simple.
You on the other hand, seem prefer to have multiple threads on the SAME subject, so good for you. The general populace are those that really shouldn't be misled this way, and need to be directed by the DEV TEAM who control this project, as to which is the correct method and direction the community should or should not take.
#crysx
Stop chasing boogeymen in shadows that don't exist!
I'm not your nemesis masquerading in a new account, I'm just a person new to bitcointalk.org
I really don't care about your code that much, but man you sure get pretty defensive about it.
I was simply making a metaphor about how personal opinions, exclusively your negative one about THIS thread, can be subjective.
Furthermore you seem to put a lot effort into prescribing the 'correct' method for establishing ANN threads. I understand that it is your opinion that ANNs "need to be directed by the DEV TEAM..." I would counter that centralizing all communications under a single authority is completely counter intuitive to the nature of decentralized blockchains. I am curious where Bitcoin's ANN thread is? link pls? (joking)(because there isn't one single thread owner for bitcoin)
So community communication will get messy sometimes in a truly decentralized project. But this thread is an attempt to clean things up- and your insinuations to the opposite are baseless.
April 03, 2018, 01:52:30 AM
A new thread was created because the old thread creator (Kai) decided he wasn't going to maintain it anymore. He's moving onto new ventures. So since his account is the only one with access to that announcement, this was the best way forward. The old announcement now links here.
I will be updating this thread for the future. At least it's a bit cleaner now since all the miners with issues are over on the old thread
I will be updating this thread for the future. At least it's a bit cleaner now since all the miners with issues are over on the old thread
This still makes no sense.
He hasn't locked the other thread, he hasn't made it public that this is what he is doing and why, he hasn't categorically stated that this is the reason why.
In fact, by doing this, he (and you to a large extent) has made this MORE of a mess than it already is by not doing these things.
#crysx
you know what doesn't make sense? building a closed source miner for 6 months built on top of GPL code and then never hiring anyone to rewrite the gpl code and then sitting on your miner, never releasing it. But hey! that's just my opinion man, just like you have yours.
Well ...
That would be true IF it was GPL code you were talking about and NOT closed source private code.
Which has nothing to do with what we are discussing here - and as a newbie profile, I assume was to just poke in the ribs.
So if it was just your 'opinion' then that is baseless and nothing worth dictating to preach. Base it on facts, and I would establish a rapport and conversation about it. Base it on hearsay and fiction like you obviously have, then I will do the same as I have done now and rebutt only to the extent that you are nothing more than bringer of bad tidings, to do divert the real issue here in THIS thread. You want a REAL cheat when it comes what you have described? Go to the spmod thread and see what you have stated in action CURRENTLY.
We have a ccminer fork internally, and DO optimize it, but never release it. That is abiding by the rules of GPL. You should read the license some day, it's enlightening to say the least.
Nice try as an attack, but a dismal fail.
#crysx
Well ...
It was just a poke in the ribs.
Likewise, it's just your 'opinion' that opening this thread creates MORE of a mess(subjective) and to ascribe any fault or actions of the previous thread owner to this thread is baseless and nothing worth dictating to preach(in your words).
Best of luck with your internal ccminer fork and CWIgm
Nice try as an attack, but a dismal fail.
#under
Reminiscent of a user who is on the forums trolling/posting on another profile that is argumentative in every way he can be.
So this is the 'new' profile you intend on using mate? Good one. Shows the gutless means that you decide to take.
In any case, your attack is moot. OUR code is just that, and we can and will do what we want with it. Period! The GPL code is restricted and governed by the licensing, and 'should' be adhered to buy the rules that govern it. It doesn't always happen that way. Why don't you accuse MicroSoft that their OS is based on opensource software and that they are using it internally, but publishing it also. I'm sure that will go down well.
As for the RVN threads. Notice - THREADS! With an 's'. This is the 'mess' that I am talking about. Unlike the use case where a single thread is used by the current owners/developers/users, multiple threads that are used at the same time on the same subject is messy. This not subjective, but factual. It is EASY for the last owner of the thread to have published that post - then lock thread. Explaining that there is a new thread because I have other projects I am working on. Simple.
You on the other hand, seem prefer to have multiple threads on the SAME subject, so good for you. The general populace are those that really shouldn't be misled this way, and need to be directed by the DEV TEAM who control this project, as to which is the correct method and direction the community should or should not take.
#crysx
Stop chasing boogeymen in shadows that don't exist!
I'm not your nemesis masquerading in a new account, I'm just a person new to bitcointalk.org
I really don't care about your code that much, but man you sure get pretty defensive about it.
I was simply making a metaphor about how personal opinions, exclusively your negative one about THIS thread, can be subjective.
Furthermore you seem to put a lot effort into prescribing the 'correct' method for establishing ANN threads. I understand that it is your opinion that ANNs "need to be directed by the DEV TEAM..." I would counter that centralizing all communications under a single authority is completely counter intuitive to the nature of decentralized blockchains. I am curious where Bitcoin's ANN thread is? link pls? (joking)(because there isn't one single thread owner for bitcoin)
So community communication will get messy sometimes in a truly decentralized project. But this thread is an attempt to clean things up- and your insinuations to the opposite are baseless.
No - not that way at all ...
I have endured way too many issues with arguments over so many things - regardless of whether you give a damn about our code or not. When someone wants to argue and a point, or accuse of doing what Rune Stensland (sp_ in this forum) is doing like you have done so in the first post, then I will ALWAYS get defensive if no such thing has occurred. So regardless of what your intention is/was, you accused us of something we have no intention of allowing to follow through with. That is why I get defensive, and why I continuously seem to defend our stance. Posts like yours make it necessary.
Other than that, opinions are just that, opinions. Metaphor or not (which it clearly was not - it was a false accusation), the fact remains that a single unified thread would cause NO confusion as opposed to multiple threads on the SAME subject matter. Maybe I should say 'active' threads instead of just 'multiple' threads. The 'old' thread is still being used and is current, while this thread is also being used and apparently current.
Why is it that the other one can't have a post to say this is the new thread and have it as the last post with the locking of the thread? Too logical to do?
Anyway, I guess we will be going around in circles with this as you seem to think there was no accusation and merely a metaphor with what you accused us of in the initial reply post, and you still think that it is all subjective here with two threads on the same subject by supposedly the same people.
No worries.
Have a great day!
#crysx
April 03, 2018, 01:35:36 AM
Silent Miner v1.0
-Mines x16r Ravencoin
-NVIDIA only
-5%-10% faster than Enemy Miner
-Only displays accepted shares
-Windows x64
-1% Dev fee
very good, like it
-Mines x16r Ravencoin
-NVIDIA only
-5%-10% faster than Enemy Miner
-Only displays accepted shares
-Windows x64
-1% Dev fee
very good, like it
April 03, 2018, 01:32:22 AM
Hey put on the old one a link to this page , not "ded start over" .... this is not serious... 
April 03, 2018, 01:28:21 AM
How to add rig names for threeeyed pool? I can't seem to find info for that on their website.
after wallet put ".name" April 03, 2018, 01:15:14 AM
⛏️⛏️⛏️ *NEW* Ravencoin Pool, miners wanted ⛏️⛏️⛏️
Join our new Pool made by the Community for the Community!
We found our first blocks so far!
https://rvn.coinblockers.com/
- Customized Nodejs driven Pool made out of steel without Yiimp crap
- Low 0.4% Pool fee
- Regulary payouts
- EU Stratum + US Stratum
- Min payouts threshold just 0.05 RVN
- Nice friendly and helpful discord community
Also feel free to join our Discord: https://discord.gg/BCweVJ9
Join our new Pool made by the Community for the Community!
We found our first blocks so far!
https://rvn.coinblockers.com/
- Customized Nodejs driven Pool made out of steel without Yiimp crap
- Low 0.4% Pool fee
- Regulary payouts
- EU Stratum + US Stratum
- Min payouts threshold just 0.05 RVN
- Nice friendly and helpful discord community
Also feel free to join our Discord: https://discord.gg/BCweVJ9
April 03, 2018, 01:13:46 AM
How to add rig names for threeeyed pool? I can't seem to find info for that on their website.
April 03, 2018, 01:06:14 AM
A new thread was created because the old thread creator (Kai) decided he wasn't going to maintain it anymore. He's moving onto new ventures. So since his account is the only one with access to that announcement, this was the best way forward. The old announcement now links here.
I will be updating this thread for the future. At least it's a bit cleaner now since all the miners with issues are over on the old thread
I will be updating this thread for the future. At least it's a bit cleaner now since all the miners with issues are over on the old thread
This still makes no sense.
He hasn't locked the other thread, he hasn't made it public that this is what he is doing and why, he hasn't categorically stated that this is the reason why.
In fact, by doing this, he (and you to a large extent) has made this MORE of a mess than it already is by not doing these things.
#crysx
you know what doesn't make sense? building a closed source miner for 6 months built on top of GPL code and then never hiring anyone to rewrite the gpl code and then sitting on your miner, never releasing it. But hey! that's just my opinion man, just like you have yours.
Well ...
That would be true IF it was GPL code you were talking about and NOT closed source private code.
Which has nothing to do with what we are discussing here - and as a newbie profile, I assume was to just poke in the ribs.
So if it was just your 'opinion' then that is baseless and nothing worth dictating to preach. Base it on facts, and I would establish a rapport and conversation about it. Base it on hearsay and fiction like you obviously have, then I will do the same as I have done now and rebutt only to the extent that you are nothing more than bringer of bad tidings, to do divert the real issue here in THIS thread. You want a REAL cheat when it comes what you have described? Go to the spmod thread and see what you have stated in action CURRENTLY.
We have a ccminer fork internally, and DO optimize it, but never release it. That is abiding by the rules of GPL. You should read the license some day, it's enlightening to say the least.
Nice try as an attack, but a dismal fail.
#crysx
Well ...
It was just a poke in the ribs.
Likewise, it's just your 'opinion' that opening this thread creates MORE of a mess(subjective) and to ascribe any fault or actions of the previous thread owner to this thread is baseless and nothing worth dictating to preach(in your words).
Best of luck with your internal ccminer fork and CWIgm
Nice try as an attack, but a dismal fail.
#under
Reminiscent of a user who is on the forums trolling/posting on another profile that is argumentative in every way he can be.
So this is the 'new' profile you intend on using mate? Good one. Shows the gutless means that you decide to take.
In any case, your attack is moot. OUR code is just that, and we can and will do what we want with it. Period! The GPL code is restricted and governed by the licensing, and 'should' be adhered to buy the rules that govern it. It doesn't always happen that way. Why don't you accuse MicroSoft that their OS is based on opensource software and that they are using it internally, but publishing it also. I'm sure that will go down well.
As for the RVN threads. Notice - THREADS! With an 's'. This is the 'mess' that I am talking about. Unlike the use case where a single thread is used by the current owners/developers/users, multiple threads that are used at the same time on the same subject is messy. This not subjective, but factual. It is EASY for the last owner of the thread to have published that post - then lock thread. Explaining that there is a new thread because I have other projects I am working on. Simple.
You on the other hand, seem prefer to have multiple threads on the SAME subject, so good for you. The general populace are those that really shouldn't be misled this way, and need to be directed by the DEV TEAM who control this project, as to which is the correct method and direction the community should or should not take.
#crysx
Stop chasing boogeymen in shadows that don't exist!
I'm not your nemesis masquerading in a new account, I'm just a person new to bitcointalk.org
I really don't care about your code that much, but man you sure get pretty defensive about it.
I was simply making a metaphor about how personal opinions, exclusively your negative one about THIS thread, can be subjective.
Furthermore you seem to put a lot effort into prescribing the 'correct' method for establishing ANN threads. I understand that it is your opinion that ANNs "need to be directed by the DEV TEAM..." I would counter that centralizing all communications under a single authority is completely counter intuitive to the nature of decentralized blockchains. I am curious where Bitcoin's ANN thread is? link pls? (joking)(because there isn't one single thread owner for bitcoin)
So community communication will get messy sometimes in a truly decentralized project. But this thread is an attempt to clean things up- and your insinuations to the opposite are baseless.
April 03, 2018, 12:41:00 AM
Price pump 300 sat to 800 sat when more?
April 03, 2018, 12:34:22 AM
A new thread was created because the old thread creator (Kai) decided he wasn't going to maintain it anymore. He's moving onto new ventures. So since his account is the only one with access to that announcement, this was the best way forward. The old announcement now links here.
I will be updating this thread for the future. At least it's a bit cleaner now since all the miners with issues are over on the old thread
I will be updating this thread for the future. At least it's a bit cleaner now since all the miners with issues are over on the old thread
This still makes no sense.
He hasn't locked the other thread, he hasn't made it public that this is what he is doing and why, he hasn't categorically stated that this is the reason why.
In fact, by doing this, he (and you to a large extent) has made this MORE of a mess than it already is by not doing these things.
#crysx
you know what doesn't make sense? building a closed source miner for 6 months built on top of GPL code and then never hiring anyone to rewrite the gpl code and then sitting on your miner, never releasing it. But hey! that's just my opinion man, just like you have yours.
Well ...
That would be true IF it was GPL code you were talking about and NOT closed source private code.
Which has nothing to do with what we are discussing here - and as a newbie profile, I assume was to just poke in the ribs.
So if it was just your 'opinion' then that is baseless and nothing worth dictating to preach. Base it on facts, and I would establish a rapport and conversation about it. Base it on hearsay and fiction like you obviously have, then I will do the same as I have done now and rebutt only to the extent that you are nothing more than bringer of bad tidings, to do divert the real issue here in THIS thread. You want a REAL cheat when it comes what you have described? Go to the spmod thread and see what you have stated in action CURRENTLY.
We have a ccminer fork internally, and DO optimize it, but never release it. That is abiding by the rules of GPL. You should read the license some day, it's enlightening to say the least.
Nice try as an attack, but a dismal fail.
#crysx
Well ...
It was just a poke in the ribs.
Likewise, it's just your 'opinion' that opening this thread creates MORE of a mess(subjective) and to ascribe any fault or actions of the previous thread owner to this thread is baseless and nothing worth dictating to preach(in your words).
Best of luck with your internal ccminer fork and CWIgm
Nice try as an attack, but a dismal fail.
#under
Reminiscent of a user who is on the forums trolling/posting on another profile that is argumentative in every way he can be.
So this is the 'new' profile you intend on using mate? Good one. Shows the gutless means that you decide to take.
In any case, your attack is moot. OUR code is just that, and we can and will do what we want with it. Period! The GPL code is restricted and governed by the licensing, and 'should' be adhered to buy the rules that govern it. It doesn't always happen that way. Why don't you accuse MicroSoft that their OS is based on opensource software and that they are using it internally, but publishing it also. I'm sure that will go down well.
As for the RVN threads. Notice - THREADS! With an 's'. This is the 'mess' that I am talking about. Unlike the use case where a single thread is used by the current owners/developers/users, multiple threads that are used at the same time on the same subject is messy. This not subjective, but factual. It is EASY for the last owner of the thread to have published that post - then lock thread. Explaining that there is a new thread because I have other projects I am working on. Simple.
You on the other hand, seem prefer to have multiple threads on the SAME subject, so good for you. The general populace are those that really shouldn't be misled this way, and need to be directed by the DEV TEAM who control this project, as to which is the correct method and direction the community should or should not take.
#crysx
April 03, 2018, 12:21:57 AM
A new thread was created because the old thread creator (Kai) decided he wasn't going to maintain it anymore. He's moving onto new ventures. So since his account is the only one with access to that announcement, this was the best way forward. The old announcement now links here.
I will be updating this thread for the future. At least it's a bit cleaner now since all the miners with issues are over on the old thread
I will be updating this thread for the future. At least it's a bit cleaner now since all the miners with issues are over on the old thread
This still makes no sense.
He hasn't locked the other thread, he hasn't made it public that this is what he is doing and why, he hasn't categorically stated that this is the reason why.
In fact, by doing this, he (and you to a large extent) has made this MORE of a mess than it already is by not doing these things.
#crysx
you know what doesn't make sense? building a closed source miner for 6 months built on top of GPL code and then never hiring anyone to rewrite the gpl code and then sitting on your miner, never releasing it. But hey! that's just my opinion man, just like you have yours.
Well ...
That would be true IF it was GPL code you were talking about and NOT closed source private code.
Which has nothing to do with what we are discussing here - and as a newbie profile, I assume was to just poke in the ribs.
So if it was just your 'opinion' then that is baseless and nothing worth dictating to preach. Base it on facts, and I would establish a rapport and conversation about it. Base it on hearsay and fiction like you obviously have, then I will do the same as I have done now and rebutt only to the extent that you are nothing more than bringer of bad tidings, to do divert the real issue here in THIS thread. You want a REAL cheat when it comes what you have described? Go to the spmod thread and see what you have stated in action CURRENTLY.
We have a ccminer fork internally, and DO optimize it, but never release it. That is abiding by the rules of GPL. You should read the license some day, it's enlightening to say the least.
Nice try as an attack, but a dismal fail.
#crysx
Well ...
It was just a poke in the ribs.
Likewise, it's just your 'opinion' that opening this thread creates MORE of a mess(subjective) and to ascribe any fault or actions of the previous thread owner to this thread is baseless and nothing worth dictating to preach(in your words).
Best of luck with your internal ccminer fork and CWIgm
Nice try as an attack, but a dismal fail.
#under
April 03, 2018, 12:03:25 AM
New whitepaper and Road map!!!
https://github.com/RavenProject/Ravencoin/blob/master/roadmap/README.md
http://ravencoin.org/Ravencoin.pdf
Ravencoin is about to change the world!!
https://github.com/RavenProject/Ravencoin/blob/master/roadmap/README.md
http://ravencoin.org/Ravencoin.pdf
Ravencoin is about to change the world!!
roadmap needs deadlines...
and about exchanges? payment gateways etc...
I think you have some misunderstandings about what kind of project this is. Its not another alt-coin controlled completely by a core development team. I know it seems trite, but you may gain more perspective about this project by joining the discord server. For instance, Dev team has stated their goal for the asset layer fork is October of 2018. Also they have stated that as a dev team their primary objective is coding the platform. Exchanges and payment gateways are a low priority for the Dev Team, but the community has so far organized listing RVN on Cryptobridge and Barterdex. This project is going to be a bit different than the shitcoins some may be used to that have a 3 month lifespan of A)mine B)lackluster POS implementation/masternode C)exit into obscurity
April 02, 2018, 11:59:47 PM
New whitepaper and Road map!!!
https://github.com/RavenProject/Ravencoin/blob/master/roadmap/README.md
http://ravencoin.org/Ravencoin.pdf
Ravencoin is about to change the world!!
https://github.com/RavenProject/Ravencoin/blob/master/roadmap/README.md
http://ravencoin.org/Ravencoin.pdf
Ravencoin is about to change the world!!
roadmap needs deadlines...
and about exchanges? payment gateways etc...
That is completely false.
Roadmaps do NOT 'need' deadlines, which is the main reason I have been preaching this fact to the masses for years. Your perception is that it does, nothing more.
The whole crypto industry is working on inconsistent misunderstandings of terms, technologies, and projects, and is unfortunately a detrimental situation for ALL that are in it.
#crysx
April 02, 2018, 11:57:21 PM
A new thread was created because the old thread creator (Kai) decided he wasn't going to maintain it anymore. He's moving onto new ventures. So since his account is the only one with access to that announcement, this was the best way forward. The old announcement now links here.
I will be updating this thread for the future. At least it's a bit cleaner now since all the miners with issues are over on the old thread
I will be updating this thread for the future. At least it's a bit cleaner now since all the miners with issues are over on the old thread
This still makes no sense.
He hasn't locked the other thread, he hasn't made it public that this is what he is doing and why, he hasn't categorically stated that this is the reason why.
In fact, by doing this, he (and you to a large extent) has made this MORE of a mess than it already is by not doing these things.
#crysx
you know what doesn't make sense? building a closed source miner for 6 months built on top of GPL code and then never hiring anyone to rewrite the gpl code and then sitting on your miner, never releasing it. But hey! that's just my opinion man, just like you have yours.
Well ...
That would be true IF it was GPL code you were talking about and NOT closed source private code.
Which has nothing to do with what we are discussing here - and as a newbie profile, I assume was to just poke in the ribs.
So if it was just your 'opinion' then that is baseless and nothing worth dictating to preach. Base it on facts, and I would establish a rapport and conversation about it. Base it on hearsay and fiction like you obviously have, then I will do the same as I have done now and rebutt only to the extent that you are nothing more than bringer of bad tidings, to do divert the real issue here in THIS thread. You want a REAL cheat when it comes what you have described? Go to the spmod thread and see what you have stated in action CURRENTLY.
We have a ccminer fork internally, and DO optimize it, but never release it. That is abiding by the rules of GPL. You should read the license some day, it's enlightening to say the least.
Nice try as an attack, but a dismal fail.
#crysx
April 02, 2018, 11:52:14 PM
New whitepaper and Road map!!!
https://github.com/RavenProject/Ravencoin/blob/master/roadmap/README.md
http://ravencoin.org/Ravencoin.pdf
Ravencoin is about to change the world!!
https://github.com/RavenProject/Ravencoin/blob/master/roadmap/README.md
http://ravencoin.org/Ravencoin.pdf
Ravencoin is about to change the world!!
roadmap needs deadlines...
and about exchanges? payment gateways etc...
Jump to: