Requires UNPNP or Port Forwarding of TCP:32348. Can someone please explain to a noob like me how to do those things please? Thank you Settings>options>network>tick box mark UPnP and that is it correct? It is already set up by default in the wallet yes but your router must support it of your using NAT/Internal/Private IP
|
|
|
In order for the private mode to work with this release, you must have have UNPNP enabled on your router OR have the port mapped correctly inbound -- this will be resolved in a future release Can I suggest changing to "Enable XCend" ? Hmm.. I'm open to suggestions on this topic...
|
|
|
In order for the private mode to work with this release, you must have have UNPNP enabled on your router OR have the port mapped correctly inbound -- this will be resolved in a future release
|
|
|
It's been over 30min and it didn't come through.
sometimes they get rejected,you can try it again and see if it goes through Is there an error message/status check if it didn't go through? Not in this release, it will be added
|
|
|
It's been over 30min and it didn't come through.
sometimes they get rejected,you can try it again and see if it goes through
|
|
|
Thanks for being patient and helping with testing :-)
|
|
|
Okay I sent a distmix this was my line distmix <destination address> 10 is that right? It went through with 0.00002 sent and 0.00001 received.
Hmm.. update being posted now for this ...
|
|
|
http://downloads.xc-official.com/release/wallets/dtm-beta/XC-v0.9.2.3x11-coin-1.0.zipI have good news: Rev 2 Beta 2 is now on mainnet! You can now download it from the url posted. This is not the final Rev 2 app. Anon features are only accessible from the command line. However, decentralised trustless mixing is working through a simple rpc command via the debug console. This is beta software. Please back up your wallet.dat before using it. Also this release changes everything to XCurrency including the %appdata% directory An updated UI will be released with the privacy mode available through the coin control page. If your testing the distmix command, read the distmix.txt in the zip PM me with any issues or questions ATCSECURE hey these are GREAT news! To the less technically sound like me: if we use this wallet, and have more than 550XC, we get to be an xnode in mainet? Do we need a new .conf file? Thanx for ur work! The details are in the zip, but this is not the final REV2 release, yes to be an XNode you need 550XC's, however for this testing the decentralized trustluess mixer does not require 550XC's.
|
|
|
http://downloads.xc-official.com/release/wallets/dtm-beta/XC-v0.9.2.3x11-coin-1.0.zipI have good news: Rev 2 Beta 2 is now on mainnet! You can now download it from the url posted. This is not the final Rev 2 app. Anon features are only accessible from the command line. However, decentralised trustless mixing is working through a simple rpc command via the debug console. This is beta software. Please back up your wallet.dat before using it. Also this release changes everything to XCurrency including the %appdata% directory An updated UI will be released with the privacy mode available through the coin control page. If your testing the distmix command, read the distmix.txt in the zip PM me with any issues or questions ATCSECURE
|
|
|
bitcad4u - I'm well aware of your support of XC from the beginning I think any reasonable person would be critical of what happened last night, but at the same time things happen in software development, I knew the schedule was aggressive and unfortunately things happen and did happen.
|
|
|
lets redirect back to testing the current release
|
|
|
I'm on IRC for those looking to test this new release out
|
|
|
so atcsecure@ubuntu12:~/rev2$ ./x11coind listunspent [ { "txid" : "4db767253f7b7b6e8ed3c5f5740e2e0457fc8230121f0ec40cafd5d1cfc7140e", "vout" : 3, "scriptPubKey" : "76a914aafea4fb96f3907b094b7806f9525e9a00cdaba688ac", "amount" : 98.99999000, "confirmations" : 51 } ] atcsecure@ubuntu12:~/rev2$ take the data from that output and create atcsecure@ubuntu12:~/rev2$ ./x11coind distmix 4db767253f7b7b6e8ed3c5f5740e2e0457fc8230121f0ec40cafd5d1cfc7140e 1 98.99999 XGxwPxnVa7tx91b5pjGXmGRmqmQ81VLjtG 1 Also with this release you can test on main-net So for the main-net testing, there is NO RISK of loosing coins, this is trustless mixing it takes up to 30minutes after you submit for a transaction to get processed for now use a 1 XC as your output amount
|
|
|
so atcsecure@ubuntu12:~/rev2$ ./x11coind listunspent [ { "txid" : "4db767253f7b7b6e8ed3c5f5740e2e0457fc8230121f0ec40cafd5d1cfc7140e", "vout" : 3, "scriptPubKey" : "76a914aafea4fb96f3907b094b7806f9525e9a00cdaba688ac", "amount" : 98.99999000, "confirmations" : 51 } ] atcsecure@ubuntu12:~/rev2$ take the data from that output and create atcsecure@ubuntu12:~/rev2$ ./x11coind distmix 4db767253f7b7b6e8ed3c5f5740e2e0457fc8230121f0ec40cafd5d1cfc7140e 1 98.99999 XGxwPxnVa7tx91b5pjGXmGRmqmQ81VLjtG 1 Also with this release you can test on main-net
|
|
|
so there are 2 new commands
atcsecure@ubuntu12:~/rev2$ ./x11coind simpledistmix error: {"code":-1,"message":"simpledistmix <destAddress> <amountToSend>\n"}
atcsecure@ubuntu12:~/rev2$ ./x11coind distmix error: {"code":-1,"message":"distmix <fromtx> <vout> <inamount> <toaddress> <outamount>\n For testing, use an outamount of 1 for the best results; a minimum fee is removed from the change.\n"} atcsecure@ubuntu12:~/rev2$
I am pushing a minor update to enable the first command as the 2nd is complicated.. give me 10 minutes
|
|
|
While I am severely pissed off at how things were handled last night by the entire team, I still have complete faith in this coin and Dan. Please XC team, learn from your mistakes and stop hurting your own project. I understand growing pains, but if Rev2 would have been released at 8pm last night, XC's name would be held high today and the price would reflect the respect.
I want to respond to this, as I don't blame anybody for being upset how things went down last night. Could it have been handled better, yes... we will we learn from this.. YES... However, it was a decision that I had to make, as I was not comfortable releasing the mainnet code in its current state and I stand by that decision. Moving forward a more formal release process will be followed. -Dan-
|
|
|
|