unfortunate but the price did not react to the news...
at least AmsterdamCoin had a new roadmap which that will help to development the project itself.
As I see in
http://coinmarketcap.com/currencies/amsterdamcoin/#charts so sad to see.
but i have a point which AMS this just beginning to start with a new roadmap, will see the next month and how the price going
a roadmap is absolutely useless - if the CURRENT state of the wallet / sync / workings are not up to par ...
issues with the wallet are going unnoticed - especially when major flaws are exposed - and kees just shrugs it off as being 'our' doing and not the wallet / daemon itself ...
major flaws with syncing - and the reason? ... orphan blocks being sent ALL over the blockchain ... i showed this proof in a previous post - also ignored with a message saying kees will 'look' at this ... instead he comes out with a 'roadmap' ... a 'plan' of things to come? ... when the current state of the wallet is NOT functioning properly? ... really? ...
flaws in rpc accessibility ... also gone ignored ... the daemon / wallet itself drops the rpc connections on a regular and consistent basis - which is also why the 'official' blockexplorer consistently lags behind ... so instead of liaising with us to FIX the issue - a roadmap is produced ... nice one kees ... this is VERY reminiscent of another dev that worked on a few other coins - like loco ... remember him? ... the dev called nightz? ... he was doing the same thing ... ignoring me - ignoring my help - ignoring ALL the warning signs of a failure about to happen ... lets see where loco the coin went? ... ummm ... o yes - it failed ...
or even soopy for that matter? ... you know who he is dont you? ... i bet you do ... i bet you know both of these devs - well ...
...
if these issues are not FIXED in the current wallet - how do you propose to have all these things in the roadmap done? ... a roadmap only equals PLANS ... its all talk until the next step is seen ... and you cant get to the next step until THIS step is FIXED ... not ignored ...
we pulled the pool from our pool list - purely because it was the ONLY wallet / daemon that was disconnecting AND causing sync issues ALL the time ... so ignore this post or not mate ... these issues NEED resolve before you can even think of following a roadmap ... unless its all vapourware that you are drumming up here of course ... in that case - just continue to ignore my posts and ignore fixing anything in the wallet - then move on to your next coins roadmap ...
some of you devs are unbelievable ...
#crysx
Look, if our coin/wallet/blockchain/RPC were so bad then how come that:
- We have a working pool: http://pool.minertopia.org/
- We are listed at 3 exchanges that are fully up to date and working
- There are constantly proof of work blocks generated
The first step of the roadmap is already in progress by the way. As we speak the Android wallet is under development. My friend helped me out and knew a android dev that we paid to create one. In fact people are binary, they stand from the side line screaming about problems or they step in and help solving problems.
#crysx I think your a bit paranoid when you compare me to random other devs that for your idea act the same as me.
kees ...
i say what i see ... and what i experience ...
if you can get this sorted - then awesome ... quark algo coins have always been some of my fav coins ...
far from being paranoid - if you actually READ what i wrote - i said it was reminiscent of what i have personally experienced ... so if ignoring the details of these issues is your thing - then so be it ... BUT - what i have stated are truths and nothing but ...
what has started as a simple compile and install - became a nightmare ... what started as a decent sync - became an issue with MANY MANY days of sync issues - and rpc contact loss ... be it as it may with the other systems that 'seem' stable - it is a FACT that these things have happened - AND - they have happened on an ongoing basis - no matter which way we tried to compile it ... so this is an INHERENT issue within the code ... if EVERYONE looked into their logs if they had synced from the start ( not just bootstrapped ) - they WILL see the orphaned blocks as a common issue within the block chain log ... these are all facts ...
look at the statements of CUSTOMERS of ams - that prove how badly the daemon / wallet syncs ... look at the notes ( yes NOTES - not just posts ) of the ams CUSTOMERS and investors about the issues they face with their wallets and the time it takes to sync - as well as the issues that accompany - and tell me they are just being paranoid about it all also ...
the coin has issues - big ones ... whether you wish to acknowledge that or not - is your business ... but from highly experienced crypto enthusiast / supporter - to another - there are issues that NEED fixing here ... im NOT hammering the coin for the sake of just exploiting ... i am actually giving you the experiences WE have faced compiling and running the coin - and so have the community members with stability and syncing ... read up mate - you will see that no matter how many posts you and i make - there ARE issues that need to be rectified ... once these issues are squashed - this coin will see heights never seen before in the community ...
otherwise - just keep your eyes closed ... its a great thing you are progressing with the roadmap - and any of the steps thereafter this one ... but if you continue to build on a faulty foundation of code - this will not end well ... this is advice - not attack ...
im done posting - or supporting ... so dont worry about my reposting anything here that is unjustified ... everything i have mentioned is justified and is only to open your eyes to the issues that will see the light of day - down the track ...
#crysx
