Why is XC frozen at polo??
It was frozen...unfroze for during the time it took for me to log in. I'm guessing that they were updating the wallet...
Topic: [XC][XCurrency] Decentralised Trustless Privacy Platform / Encrypted XChat / Pos - page 353. (Read 1484189 times)
September 16, 2014, 12:14:12 PM
September 16, 2014, 12:12:19 PM
Why is XC frozen at polo??
It was frozen...unfroze for during the time it took for me to log in. I'm guessing that they were updating the wallet... 
September 16, 2014, 12:09:18 PM
Why is XC frozen at polo??
Seems to be working fine.
September 16, 2014, 12:06:38 PM
What port does the wallet need to operate? I mean just have connections to the XC network, because I think my school has the port blocked that it needs.
Port 32348.
Check it here: http://www.yougetsignal.com/tools/open-ports/
You mean school school? That's so cool -- you probably have a bigger stack than the rest of us put together.
I am talking about college btw.
OK - lol - for a minute there I thought you were 12.
September 16, 2014, 12:05:25 PM
I think I have tor running correctly with XC and was pretty easy. Here is a short guide of what I did on windows 7.
Download and run the Tor Browser.
https://www.torproject.org/download/download-easy.html.en
Leave the Tor Browser open or you lose the connection.
Start > %appdata%
Go to xcurrency folder and set xcurrency.conf as follows. (This file is also in the Xcurrency install location so you can just copy it to appdata > xcurrency.)
onlynet=tor
proxy=127.0.0.1:9150
addnode=ziydan6mhjv4uixx.onion
addnode=gbigfs7reoscr2xs.onion
addnode=qwr3je6njcwvo2rw.onion
addnode=d2hc6in7jaczu3av.onion
Launch XC
Download and run the Tor Browser.
https://www.torproject.org/download/download-easy.html.en
Leave the Tor Browser open or you lose the connection.
Start > %appdata%
Go to xcurrency folder and set xcurrency.conf as follows. (This file is also in the Xcurrency install location so you can just copy it to appdata > xcurrency.)
onlynet=tor
proxy=127.0.0.1:9150
addnode=ziydan6mhjv4uixx.onion
addnode=gbigfs7reoscr2xs.onion
addnode=qwr3je6njcwvo2rw.onion
addnode=d2hc6in7jaczu3av.onion
Launch XC
September 16, 2014, 11:59:25 AM
Why is XC frozen at polo??
September 16, 2014, 11:57:46 AM
Feel free to retweet kristovs response to my XC MOON tweet
September 16, 2014, 11:54:22 AM
What port does the wallet need to operate? I mean just have connections to the XC network, because I think my school has the port blocked that it needs.
Port 32348.
Check it here: http://www.yougetsignal.com/tools/open-ports/
You mean school school? That's so cool -- you probably have a bigger stack than the rest of us put together.
I am talking about college btw.
I was thinking you were 13 to 15 years old ahah
September 16, 2014, 11:52:43 AM
XC v2.49 RC2 - now available for download, if your running RC1, please upgrade to RC2
http://downloads.xc-official.com/testing/XCurrency_2.49_RC2.exe
bump for awareness
There's now a readme.txt for basic Xmixer setup:
http://downloads.xc-official.com/testing/readme.txt
September 16, 2014, 11:51:37 AM
Incase people are wondering, I haven't disappeared I'm just working closely with our mobile team. I'm also very busy with personal things.
September 16, 2014, 11:48:12 AM
Someone really does not want us going through 160k.....
September 16, 2014, 11:40:03 AM
September 16, 2014, 11:28:27 AM
XC v2.49 RC2 - now available for download, if your running RC1, please upgrade to RC2
http://downloads.xc-official.com/testing/XCurrency_2.49_RC2.exe
bump for awareness
September 16, 2014, 11:20:45 AM
Hey,
Thanks for the response
. Yeah I've read that doc (multiple times) and basically I just want to know the detailed process of what happens to "private payments". What I need confirming is:
Thanks for the response
. Yeah I've read that doc (multiple times) and basically I just want to know the detailed process of what happens to "private payments". What I need confirming is:- "There might not be enough nodes making private payments at a given time, causing transactions to wait or be cancelled". This leads me to believe that ONLY nodes (node being, online wallet client) making private payments at the same time as you (and XMixers) are involved in forwarding the fragments? Or is every node involved? This definitely needs confirming first and foremost.
Yes, if a user isn't sending XC at a given time then his/her Xnode will not participate in a private transaction.
But if a user runs an Xmixer it will be available to participate whenever there aren't enough normal Xnodes for a given transaction.
Quote
- When you send a private payment, what happens to it? Is it broken down in to smaller fragments (how many exactly, a random number depending on the size of the TX or what?) and sent to other online wallets (whose balances cover the size of the fragment of course I assume).
The algorithm for fragmenting randomises the fragment size and the number of fragments.
The balances of Xnodes mixing a transaction will need to be greater than or equal to the sum of some (not all) other fragments in the transaction.
Quote
Then when a node (online wallet) receives a fragment, what happens there?: [/li][/list]
- Do the coins contained in that fragment get "tumbled" with the wallet balance of the node, or just get forwarded to another node?
- Do the coins contained in that fragment get "tumbled" with the wallet balance of the node, or just get forwarded to another node?
Neither actually. The mixing is a lot more sophisticated.
- It's roughly a group_sig transaction as implemented in Coinshuffle. Check that out.
- The transaction is between participating nodes, so each node doesn't act on its own.
- When a node initiates a payment, the fragments it creates aren't necessarily part of the same transaction. Each fragment can be on a completely different mixing transaction.
- The forwarding node doesn't get just the fragment; it gets the whole transaction.
- Therefore it doesn't even know which fragment belongs to who, and how much each fragment is.
- It checks the transaction to make sure it includes its own fragment, signs the transaction, and the whole thing goes ahead.
- If any node doesn't sign, the mesh network resyncs (which happens continually btw) and carries on.
Quote
- When the fragment gets forwarded (from the node) to another node, does one fragment get sent to one node or does each fragment get further broken down in to multiple (how many?) smaller fragments which get sent to multiple (how many) other nodes? Basically, does it only split in to fragments when it comes from the sender, or does each node further split it in to smaller fragments?
Each node making a payment will fragment that payment.
This means nodes forwarding fragments are also making their own payments (in fragments).
There's no way of distinguishing between a node's own fragments and the fragments it's forwarding.
Quote
- How many times does this process happen?
* Does each fragment pass through a specific number of nodes or a random number until it finds its destination?
* Is there a minimum number of nodes a fragment has to pass through?
* Does each fragment pass through a specific number of nodes or a random number until it finds its destination?
* Is there a minimum number of nodes a fragment has to pass through?
I'm not sure on this point, but I think a single pass is all that's necessary.
Quote
- XMixer: I'm assuming only large payments get sent through the XMixer (how large does it have to be to go through there? Does this depend on the size of the currently online nodes wallets compared to the TX size? Or is it "anything above [insertsizehere] goes through mixer?) I'm assuming larger payments get sent to the mixer in order to get broken down in to many small fragments for the nodes to handle? Or do transactions large enough for the mixer simply go "sender > Mixer(tumble) > Receiver"?
Small transactions will end up going through an Xmixer if, at a given time, other Xnodes aren't transacting.
The Xnodes themselves do the fragmenting, not just Xmixers.
Xmixers therefore only receive fragments.
This means that Xmixers (and Xnodes when they forward a tx) won't see large transactions as distinct from small ones. It's all the same to them.
Quote
I could go on and on making assumptions and asking questions here mate.
I won't part with my money if I don't understand how the system works.
If there's some info or a document somewhere I've totally missed please forgive me.
If not, looking forward to hearing how this thing really works.
I won't part with my money if I don't understand how the system works.
If there's some info or a document somewhere I've totally missed please forgive me.
If not, looking forward to hearing how this thing really works.
That's a respectable position, and a low-risk one.
We're going to publish a full scholarly exposition of XC's tech in due course (i.e. probably around Rev 3 when we launch publicly).
Those who think XC is worth investing in now will stand to gain more when it succeeds.
September 16, 2014, 11:19:31 AM
Hey,
Thanks for the response
. Yeah I've read that doc (multiple times) and basically I just want to know the detailed process of what happens to "private payments". What I need confirming is:- "There might not be enough nodes making private payments at a given time, causing transactions to wait or be cancelled". This leads me to believe that ONLY nodes (node being, online wallet client) making private payments at the same time as you (and XMixers) are involved in forwarding the fragments? Or is every node involved? This definitely needs confirming first and foremost.
- When you send a private payment, what happens to it? Is it broken down in to smaller fragments (how many exactly, a random number depending on the size of the TX or what?) and sent to other online wallets (whose balances cover the size of the fragment of course I assume). Then when a node (online wallet) receives a fragment, what happens there?:
- When the fragment gets forwarded (from the node) to another node, does one fragment get sent to one node or does each fragment get further broken down in to multiple (how many?) smaller fragments which get sent to multiple (how many) other nodes? Basically, does it only split in to fragments when it comes from the sender, or does each node further split it in to smaller fragments?
- How many times does this process happen?
* Does each fragment pass through a specific number of nodes or a random number until it finds its destination?
* Is there a minimum number of nodes a fragment has to pass through?
- XMixer: I'm assuming only large payments get sent through the XMixer (how large does it have to be to go through there? Does this depend on the size of the currently online nodes wallets compared to the TX size? Or is it "anything above [insertsizehere] goes through mixer?) I'm assuming larger payments get sent to the mixer in order to get broken down in to many small fragments for the nodes to handle? Or do transactions large enough for the mixer simply go "sender > Mixer(tumble) > Receiver"?
Basically with the way this technology has been explained, I guarantee every investor in your coin has his own little fantasy in his head on how this process actually works. What I'm asking for is to know the exact process and all the variables (and dependencies) of a private payment. No wonder this coins graph is a straight line, not many people would be willing to invest in a technology they don't understand or I definitely wouldn't at least. AND it's not open source on top of that (understandably though).
I won't part with my money if I don't understand how the system works. Again, sorry if I come off as a prick.
Looking forward to hearing how this process works, because all the fantasies in my head are really good. But that's the thing it could be anything all the info I've read is so open to interpretation. And I'm here questioning whether that's intentional or not. If there's some info or a document somewhere I've totally missed please forgive me.
If not, looking forward to hearing how this thing really works.
Bumping this up for Synechist. for definitive answer.
September 16, 2014, 11:06:11 AM
XC v2.49 RC2 - now available for download, if your running RC1, please upgrade to RC2
http://downloads.xc-official.com/testing/XCurrency_2.49_RC2.exe
Thank you DAN we are proud of your work in this community Hat down for you sir.
P.S: come in here and get some cheering
P.S.2: could you reply to my PM? thx
September 16, 2014, 11:03:20 AM
Nice work ATC... You have done the community proud.
Bittrex vol up to 43 BTC now, it seems to be talking over slightly from MP.. 162 k on there as well.. Loving this slow grinding move up... We finally seem to be solid...
Bittrex vol up to 43 BTC now, it seems to be talking over slightly from MP.. 162 k on there as well.. Loving this slow grinding move up... We finally seem to be solid...
September 16, 2014, 11:02:22 AM
XC v2.49 RC2 - now available for download, if your running RC1, please upgrade to RC2
http://downloads.xc-official.com/testing/XCurrency_2.49_RC2.exe
September 16, 2014, 11:00:50 AM
What port does the wallet need to operate? I mean just have connections to the XC network, because I think my school has the port blocked that it needs.
Port 32348.
Check it here: http://www.yougetsignal.com/tools/open-ports/
You mean school school? That's so cool -- you probably have a bigger stack than the rest of us put together.
I am talking about college btw.
I was thinking you were 13 to 15 years old ahah
September 16, 2014, 10:55:35 AM
Synech don't know if you lost it but Kristov Atlas as well was asking for more info..
https://twitter.com/XCurrency/status/511665384614023168
Edit: I see you ve already replied to Atlas
https://twitter.com/XCurrency/status/511665384614023168
Edit: I see you ve already replied to Atlas
Just tweeted at him as well: https://twitter.com/XCurrency/status/511885933260865536
Let's retweet and respond to that folks. Make some noise!
Jump to: