I don't know if you guys really want to play this game just yet. ATCSecure has always said that this is just a coinmixer and not "NSA" level type anonymity. His rev 3 will get to that level. If somehow, the answer is correct, you guys will just create a lot of FUD that ATCSecure never said rev 1 will deliver.... you mean. No one should test the anonymity in case they can break it? bit of an odd way to approach a feature set. In my line of work we have always tested code as hard as we possibly can until it broke. Then we knew how to make it better. I hold DRK and I hold XC I evangelise for neither. I just want the tech behind my coins to be as good as possible, if people break it all the better. Then the dev knows what needs to be fixed. Sure you should test it, but don't take it like it's an official representation of what XC will ultimately deliver at the end. The test is on the sending of it arriving at the destination, not on how "secure" or "anonymous" the final XC will deliver. Everyone knows that coin mixing isn't 100% anonymous and ATCSecure have already said that for rev 1, it's just a generic mixer that won't deliver 100% anonymity. DRK trolls will run with this and FUD this to death. There is no need to create FUD for them. Now, if REV3 anonymity fails, then that's a different story. This is good data and actually a very simple fix, which will be included in v1.36.... Thank you! |
|
|
|
|
I have completed the mainnet testing this morning of the XC's anonymous mixer solution and will be releasing the user guides for both the XNODE and using the "sendfrommixer" command. As this feature is still "beta", limit your risk with small transactions. Currently it is hardcoded to limit a max of 10 XC's per request, however for my testing I am using fractional amounts (ie: 0.01 or less)
ATCSECURE
|
|
|
|
so will nayone reply to me? -_-
Same for me, no reward for minting but it seems it can take time, so .. I have coins stacked for more than a day... the last reward estimate ginished 1 hour ago but still nothing. Proof of Stake is pure lottery based on the coin weight/age, I will be posting some details later today w/ the guides on the proof of stake function. |
|
|
|
The user guide for the XNODES will be release later today.. as well as a basic guide on how to "mint" using your wallet. If your wallet is locked and you want to enable minting with out unlocking, the best approach is to use this command [this is for users who locked/encrypted the wallet] walletpassphrase <passphrase> <timeout> [mintonly] so example would be walletpassphrase mypasswordgoeshere 999999999 true ATCSECURE |
|
|
|
Is atcsecure still planning on giving an update tonight for future plans as well as more detailed report on xnodes?
Anyone know?
yes, dev posted this earlier. Sorry but this is going to be fairly brief as I'm exhausted - Future Plans - Finalize Business Plan - Identify key market potential opportunities - Market analysis for high growth opportunities - XC Foundation - Structured Corporate Entity - Android Wallet - Release REV2 - REV2 is a major upgrade to the system, using the existing REV1 code. It will support a decentralized learning trust system and be not only anonymous but have protection against various attack vectors - Post REV2 is Wallet improvements and Working today's the Retail Market Space and Point of Sales and ATM's. A cost separate analysis will be done on this - Wallet Updates to include encrypted IM, encrypted IRC type communications - Wallet Updates to support new applications (will update) - Completing the Android wallet with the Mobile solution mentioned above - That is the current high level plan, I will create a more formal way to present this and to keep it updated so that is available 24/7 - XNODE XNODE is in the wallet, the batch files run it either on mainnet or testnet. Unfortunately I was not able to complete the testing tonight. This will happen tomorrow with a basic user guide on how to set it up ATCSECURE |
|
|
|
I'm on block 23420 in the updated windows wallet.
Do I have to wait a certain time period before my coins stake?
thats the correct block Yes staking is random and can take up to 30days |
|
|
|
|
Please hold off on main-net usage, due to the fork, the timeline is pushed out a little, I will provide more details shortly on how to use XNODE
|
|
|
|
Mintpal back online!
Pos Blocks are working as they should and moving fast... if your not staking, upgrade to v1.33
Thanks,
ATCSECURE
can we stake and run an xnode from the same wallet? do we need 2 different wallets? IS running an xnode going to run the risk of being a target for hackers? I am thinking I should probably use it on an isolated network? Any opinions? Seems I might want to look into secure that computer better as well. Yes running an XNODE puts you in a different risk category, I would have a completely separate wallet for an XNODE |
|
|
|
Linux users can pull from github to get the v1.33 updates/commits OMG, forked on my several nodes. A little complaint, why not give the users a period of time to upgrade? For example, Peercoin allow users to upgrade in a month, I think we can allow users to upgrade in about 24~48 hours though in the early stage. BTW, I don't know what's the difference between 32 and 33. Currently, xc-release.rar is 32, but the latest one at /release/wallets/ is 33. @atcsecure, everything takes time, don't hurry if you have solid basis. xc-release has been updated as well. Yes I was giving users time to upgrade, unfortunately the fork required an immediately resolution.. I agree, people need time to upgrade :-) Okay, I need to catch some fresh air for a bit, and then will provide a quick summary of the XNODE that is in this release. |
|
|
|
Im in version 1.32 are we in block 23296? as I am..
for the guy above the correct wallet is in the update link in the first page
yes this is correct block height now Current wallets are available at http://xc-official.com/release/Thank you, Why all this mess on this release? I work for a very LARGE corporation that has 20k people in its IT area and even with all of our assets and months of testing things will get released into production that immediately have to be patched for unseen circumstances. atcsecure is doing a bang up job and if you feel this is a mess then perhaps you should go make your own coin and prove how it is done. Else don't bother posting your nonsensical FUD. Hey man I am here since page one trying to bring constructing discussions read back my post history I was just stating the Obvious that it was indeed a bit of a mess release. I did not want to offend the Dev work that I truly respect and I can understand that something might not work on releases that is why I was asking what it did not work. I think you should a bit chill and humble yourself and make your brain work a bit more before saying FUD FUD FUD The issue was the fork, not the release.. This release was to address that issue only and had to be made available immediately for everybody to get on the correct chain. The release did not cause the fork, it was done to resolve the fork. Thank you for your clarification and sorry If I sounded disrespectful in my previous post was not at all my Intention I wanted just to know the reason of the fork and I was thinking was due to the different versions of the wallets. I truly respect all the effort you are putting into this. No worries... and no disrespect taken... The users running v1 forked onto a separate chain, anybody on v4 and up was okay.. |
|
|
|
|
Mintpal back online!
Pos Blocks are working as they should and moving fast... if your not staking, upgrade to v1.33
Thanks,
ATCSECURE
|
|
|
|
block moving fast. now on 23371. and even more right now. am i on right track? Yes that is correct |
|
|
|
Linux users can pull from github to get the v1.33 updates/commits |
|
|
|
Im in version 1.32 are we in block 23296? as I am..
for the guy above the correct wallet is in the update link in the first page
yes this is correct block height now Current wallets are available at http://xc-official.com/release/Thank you, Why all this mess on this release? I work for a very LARGE corporation that has 20k people in its IT area and even with all of our assets and months of testing things will get released into production that immediately have to be patched for unseen circumstances. atcsecure is doing a bang up job and if you feel this is a mess then perhaps you should go make your own coin and prove how it is done. Else don't bother posting your nonsensical FUD. Hey man I am here since page one trying to bring constructing discussions read back my post history I was just stating the Obvious that it was indeed a bit of a mess release. I did not want to offend the Dev work that I truly respect and I can understand that something might not work on releases that is why I was asking what it did not work. I think you should a bit chill and humble yourself and make your brain work a bit more before saying FUD FUD FUD The issue was the fork, not the release.. This release was to address that issue only and had to be made available immediately for everybody to get on the correct chain. The release did not cause the fork, it was done to resolve the fork. |
|
|
|
Im in version 1.32 are we in block 23296? as I am..
for the guy above the correct wallet is in the update link in the first page
yes this is correct block height now Current wallets are available at http://xc-official.com/release/ |
|
|
|
"REV2 will have a solution to the bad actor problem. Using a dynamic learning trust system"
Create Xnode - steal coins.
Shutdown Xnode - Move Coins to new Xnode
steal coins.
Shutdown Xnode - Move Coins to new Xnode
Rinse, repeat.
Cant wait to get started.
Lol, good luck with your uber hax skillz /facepalm Can someone explain if that is a potential risk? I know it's probably FUD, but it seems somewhat "logic", anyone to explain? He wants people to sell XC and buy DRK, read his previous posts. XC and DRK are the two strongest anon Alts. XC appears to be developing tech very quickly however. Oh, someone already stole 1000 DRK, so people should not be throwing stones. There is no risk, the trust system is designed to prevent this and other potential attack vectors |
|
|
|
|
Current block height
"blocks" : 23295
if your over that then your forked - del blk*.dat files to resync
block explorer is on wrong fork, I've already reached out to the admin
if your stuck at 23288 - thats the checkpoint block, it will update
|
|
|
|
the fork fud was tf2 polo wallet manager updating to the latest wallet release and syncing the blockchain after verifying it wasnt a fork.. however to the person asking if the block explorer is on the wrong fork vs the people asking. well the block explorer shows 23420 blocks and i show 23294. since i recieved a transaction from poloniex a handful of minutes ago i can assume the blockchain explorer is incorrect. though to that end i am now stuck syncing 1 block behind where poloniex shows height of 23295. how am i left in the past why?!
The correct height is 23293, anybody above that height should resync w/ the blockchain You can resync by removing the blk*.dat files in your %appdata%\roaming\X11Coin folder - always backup your wallet before doing anything |
|
|
|
|
Show Posts
