Have you problem with manual payout? I make three payouts and dont get coins to wallets
Only one payout was successfull on 26-05-2014
i send him pm on this forum ;-)
i have unsuccefull all payments from 01-06 to today
Topic: Conspiracy Coin - page 123. (Read 265462 times)
Have you problem with manual payout? I make three payouts and dont get coins to wallets
Only one payout was successfull on 26-05-2014
i send him pm on this forum ;-)
i have unsuccefull all payments from 01-06 to today
Dev, please get this added to Bittrex.. if possible 
Dev's can't get coins added to exchanges, they can put a request in and then normally there is a vote based system for the exchange to adopt the coin. But anyone can do this, you only need to be interested in the coin. Anyone can request to an exchange that a coin be added.I think dev's should dev and the community should vote on the exchanges.
Dev, please get this added to Bittrex.. if possible
It's on poloniex which is a much, much bigger exchange than bittrex.
Dev, please get this added to Bittrex.. if possible
Have you problem with manual payout? I make three payouts and dont get coins to wallets
Only one payout was successfull on 26-05-2014
Have you problem with manual payout? I make three payouts and dont get coins to wallets
Only one payout was successfull on 26-05-2014
You have to specify a VERSION and a LOCATION. There is no way round this. Some use a suffix and some don't.
Coding is not perfect - look at how buggy Windows can be. The best a developer can do is fix bugs as they arise. But, as the wallets use numerous independent libraries which are constantly updated, it starts to get tricky.
There are thousands of threads on Bitcointalk about compiling wallets, simply because it's not straight-forward.
Sounds like you haven't got a clue matey, I suggest you stick to the drip fed coins.
If you're using linux I'm sure you can check you have the required libraries and the qt file matches the locations. Simple for most people who know how to actually use linux.
Buy a Mac or a PC if you don't know what you're doing.
Oh wait, let's blame everyone else for our own stupidity instead.
Is it really a stupidity I want the source to compile independently of libboost version and specific location?
I know it could be done and you too. Fixing sources 'on the fly' is not a real solution at all.
Coding is not perfect - look at how buggy Windows can be. The best a developer can do is fix bugs as they arise. But, as the wallets use numerous independent libraries which are constantly updated, it starts to get tricky.
There are thousands of threads on Bitcointalk about compiling wallets, simply because it's not straight-forward.
Sounds like you haven't got a clue matey, I suggest you stick to the drip fed coins.
If you're using linux I'm sure you can check you have the required libraries and the qt file matches the locations. Simple for most people who know how to actually use linux.
Buy a Mac or a PC if you don't know what you're doing.
Oh wait, let's blame everyone else for our own stupidity instead.
Is it really a stupidity I want the source to compile independently of libboost version and specific location?
I know it could be done and you too. Fixing sources 'on the fly' is not a real solution at all.
Sounds like you haven't got a clue matey, I suggest you stick to the drip fed coins.
If you're using linux I'm sure you can check you have the required libraries and the qt file matches the locations. Simple for most people who know how to actually use linux.
Buy a Mac or a PC if you don't know what you're doing.
Oh wait, let's blame everyone else for our own stupidity instead.
Is it really a stupidity I want the source to compile independently of libboost version and specific location?
I know it could be done and you too. Fixing sources 'on the fly' is not a real solution at all.
I've just compiled on Windows with libboost 1_53 and works fine
No, it doesn't compile with libboost 1.55 either.
The reason is specific libboost location in the line #18 of conspiracycoin-qt.pro
It is not neccesary at all and results with an error if the lib is different version or not in the specyfic location. libboost 1.55 is also not really required.
Could be fixed. Clearing the suffix fixed it for me after long research and you could make the suffix being recognied properly by qt.pro file proper settings.
Code:
[quote author=ConspiracyCoin link=topic=590841.msg7199410#msg7199410 date=1402247103]
You're going through a learning curve all developers/compilers go through! We've been through it with both Windows and Mac - but we didn't blame specific developers. We just tested and researched until we got everything right.
Again, it's NOT a bug! It depends on the version of BOOST you have downloaded. There are MANY versions of boost and some don't work very well!
You're going through a learning curve all developers/compilers go through! We've been through it with both Windows and Mac - but we didn't blame specific developers. We just tested and researched until we got everything right.
Again, it's NOT a bug! It depends on the version of BOOST you have downloaded. There are MANY versions of boost and some don't work very well!
No, it doesn't compile with libboost 1.55 either.
The reason is specific libboost location in the line #18 of conspiracycoin-qt.pro
It is not neccesary at all and results with an error if the lib is different version or not in the specyfic location. libboost 1.55 is also not really required.
Could be fixed. Clearing the suffix fixed it for me after long research and you could make the suffix being recognied properly by qt.pro file proper settings.
Code:
[quote author=ConspiracyCoin link=topic=590841.msg7199410#msg7199410 date=1402247103]
You're going through a learning curve all developers/compilers go through! We've been through it with both Windows and Mac - but we didn't blame specific developers. We just tested and researched until we got everything right.
Again, it's NOT a bug! It depends on the version of BOOST you have downloaded. There are MANY versions of boost and some don't work very well!
You're going through a learning curve all developers/compilers go through! We've been through it with both Windows and Mac - but we didn't blame specific developers. We just tested and researched until we got everything right.
Again, it's NOT a bug! It depends on the version of BOOST you have downloaded. There are MANY versions of boost and some don't work very well!
No, it doesn't compile with libboost 1.55 either.
The reason is specific libboost location in the line #18 of conspiracycoin-qt.pro
It is not neccesary at all and results with an error if the lib is different version or not in the specyfic location. libboost 1.55 is also not really required.
Could be fixed. Clearing the suffix fixed it for me after long research and you could make the suffix being recognied properly by qt.pro file proper settings.
You're going through a learning curve all developers/compilers go through! We've been through it with both Windows and Mac - but we didn't blame specific developers. We just tested and researched until we got everything right.
Again, it's NOT a bug! It depends on the version of BOOST you have downloaded. There are MANY versions of boost and some don't work very well!
The success of Conspiracy Coin is not dependent on Bitcointalk - next week we start to spread our wings after building up content on the blog.
Again, it's NOT a bug! It depends on the version of BOOST you have downloaded. There are MANY versions of boost and some don't work very well!
The success of Conspiracy Coin is not dependent on Bitcointalk - next week we start to spread our wings after building up content on the blog.
Right, at least you answered. Maybe there is a hope for this coin.
Please see the discussion here. This in possible solution.
https://bitcointalksearch.org/topic/m.7195545
Please see the discussion here. This in possible solution.
https://bitcointalksearch.org/topic/m.7195545
It wasn't a BUG!
Compiling source can be a pain in the ass! There are many potential settings, flags, library issues, etc. What works on one OS may not work on another!
We've spent many, many hours creating stable environments for compiling on Windows, Mac and Linux, but so have many other developers.
Yes, I did.
I am just asking all developers of abandoned coins for the last time to fix their bugs that remains from the launch time in the code and are not fixed since then.
I am angry for massive abandonment of coins and I have the right. Dev is someone supposed to take care for the project and when I see I pointed out basic bug that are easy to fix and they ignore I have to tell the same as warning to the community.
Compiling source can be a pain in the ass! There are many potential settings, flags, library issues, etc. What works on one OS may not work on another!
We've spent many, many hours creating stable environments for compiling on Windows, Mac and Linux, but so have many other developers.
Marada just posted this about another coin.
Yes, I did.
I am just asking all developers of abandoned coins for the last time to fix their bugs that remains from the launch time in the code and are not fixed since then.
I am angry for massive abandonment of coins and I have the right. Dev is someone supposed to take care for the project and when I see I pointed out basic bug that are easy to fix and they ignore I have to tell the same as warning to the community.
Right, at least you answered. Maybe there is a hope for this coin.
Please see the discussion here. This is possible solution.
https://bitcointalksearch.org/topic/m.7195545
Please see the discussion here. This is possible solution.
https://bitcointalksearch.org/topic/m.7195545
It wasn't a BUG!
Compiling source can be a pain in the ass! There are many potential settings, flags, library issues, etc. What works on one OS may not work on another!
We've spent many, many hours creating stable environments for compiling on Windows, Mac and Linux, but so have many other developers.
Yes, I did.
I am just asking all developers of abandoned coins for the last time to fix their bugs that remains from the launch time in the code and are not fixed since then.
I am angry for massive abandonment of coins and I have the right. Dev is someone supposed to take care for the project and when I see I pointed out basic bug that are easy to fix and they ignore I have to tell the same as warning to the community.
Compiling source can be a pain in the ass! There are many potential settings, flags, library issues, etc. What works on one OS may not work on another!
We've spent many, many hours creating stable environments for compiling on Windows, Mac and Linux, but so have many other developers.
Marada just posted this about another coin.
Yes, I did.
I am just asking all developers of abandoned coins for the last time to fix their bugs that remains from the launch time in the code and are not fixed since then.
I am angry for massive abandonment of coins and I have the right. Dev is someone supposed to take care for the project and when I see I pointed out basic bug that are easy to fix and they ignore I have to tell the same as warning to the community.
This is line 18 - this not a bug!
if you've done any compiling you know this changes based on the boost version used
Quote
LIBS += -lboost_system-mgw46-mt-s-1_53 -lboost_filesystem-mgw46-mt-s-1_53 -lboost_program_options-mgw46-mt-s-1_53 -lboost_thread-mgw46-mt-s-1_53
if you've done any compiling you know this changes based on the boost version used
Marada just posted this about another coin.
Yes, I did.
I am just asking all developers of abandoned coins for the last time to fix their bugs that remains from the launch time in the code and are not fixed since then.
I am angry for massive abandonment of coins and I have the right. Dev is someone supposed to take care for the project and when I see I pointed out basic bug that are easy to fix and they ignore I have to tell the same as warning to the community.
Actually I disagree that a developer is responsible for maintaining a project past its creation and launch. At that point, once a coin is launched, its up to the community to maintain the health of the coin in my opinion.
If a coin is launched and then goes to shit, thats not the developers fault. That's the communities fault, and I guess if the community doesn't care about a coin enough to maintain it, its not worth maintaining.
It wasn't a BUG!
Compiling source can be a pain in the ass! There are many potential settings, flags, library issues, etc. What works on one OS may not work on another!
We've spent many, many hours creating stable environments for compiling on Windows, Mac and Linux, but so have many other developers.
Yes, I did.
I am just asking all developers of abandoned coins for the last time to fix their bugs that remains from the launch time in the code and are not fixed since then.
I am angry for massive abandonment of coins and I have the right. Dev is someone supposed to take care for the project and when I see I pointed out basic bug that are easy to fix and they ignore I have to tell the same as warning to the community.
Compiling source can be a pain in the ass! There are many potential settings, flags, library issues, etc. What works on one OS may not work on another!
We've spent many, many hours creating stable environments for compiling on Windows, Mac and Linux, but so have many other developers.
Marada just posted this about another coin.
Yes, I did.
I am just asking all developers of abandoned coins for the last time to fix their bugs that remains from the launch time in the code and are not fixed since then.
I am angry for massive abandonment of coins and I have the right. Dev is someone supposed to take care for the project and when I see I pointed out basic bug that are easy to fix and they ignore I have to tell the same as warning to the community.
Marada just posted this about another coin.
Yes, I did.
I am just asking all developers of abandoned coins for the last time to fix their bugs that remains from the launch time in the code and are not fixed since then.
I am angry for massive abandonment of coins and I have the right. Dev is someone supposed to take care for the project and when I see I pointed out basic bug that are easy to fix and they ignore I have to tell the same as warning to the community.
Please see my last post made 20th of may at the same forum with a clear solution for the bug that remained in the Copperlark sources fo almoust one year. No code update has been done since!
Marada just posted this about another coin.
Did you PM the Dev about the problem?
Doesn't the dev read ANN forum?
Honestly I don't belive. You can try out and see what happen.
Posting on facebook, telling stories? 13 years old kid can do this.
What is the measure of coin value if not the devs interestment in how does their software work?
Did you PM the Dev about the problem?
Doesn't the dev read ANN forum?
Honestly I don't belive. You can try out and see what happen.
Posting on facebook, telling stories? 13 years old kid can do this.
What is the measure of coin value if not the devs interestment in how does their software work?
Jump to: