|
_evolution_
|
 |
August 10, 2014, 01:49:50 PM |
|
Trying to send synechist a message and getting error message 'message encryption failed'.
No issues here. Been chatting with multiple people. Are you using RC3? On what operating system? The issue can be reproduced on OS X only. Here are my details: {
"version" : "v0.9.2.47h.XCurrency-2.47",
"protocolversion" : 71030,
"walletversion" : 60000,
"blocks" : 84742,
"moneysupply" : 5522632.98602700,
"connections" : 6,
"proxy" : "",
"difficulty" : 5205.79639598,
"testnet" : false,
"keypoololdest" : 1405241968,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"unlocked_until" : 0,
"errors" : ""
}
Hey, sorry, I was without internet for a couple days. Yes, I am also running OSX, the latest version. Has this been addressed yet? I saw someone else a page or two ago said they got theirs to work after getting this message. I don't think the issue is fixed, still getting "message encryption failed" on OS X. I was wondering if CryptoGretzky is running XChat on OS X without issues. |
|
|
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
infinitechaos
|
|
August 10, 2014, 01:57:51 PM |
|
I don't think the issue is fixed, still getting "message encryption failed" on OS X. I was wondering if CryptoGretzky is running XChat on OS X without issues.
OK, this guy seems to have a working OSX wallet. Then again, my wallet works, it's just the XChat feature where I get this error message.
Well at least one fix happened. I now have a working OSX wallet, but I wasn't complaining about that every five minutes. Yes, it is still buggy, and yes I'm a patient adult.
|
|
|
|
|
_evolution_
|
|
August 10, 2014, 02:07:40 PM |
|
I don't think the issue is fixed, still getting "message encryption failed" on OS X. I was wondering if CryptoGretzky is running XChat on OS X without issues.
OK, this guy seems to have a working OSX wallet. Then again, my wallet works, it's just the XChat feature where I get this error message.
Well at least one fix happened. I now have a working OSX wallet, but I wasn't complaining about that every five minutes. Yes, it is still buggy, and yes I'm a patient adult.
About OS X: I've never seen issues with the wallet itself, only the XChat but that's not a big concern, the tor stick works just fine. |
|
|
|
|
synechist
Legendary
 Offline
Activity: 1190
Merit: 1000
To commodify ethicality is to ethicise the market
|
|
August 10, 2014, 02:12:52 PM |
|
|
Co-Founder, the Blocknet
|
|
|
|
Teka (OP)
|
|
August 10, 2014, 02:13:58 PM |
|
Some of you raised some suggestions for the store so we decided to accept litecoin and bitcoin.
|
|
|
|
|
PowderMonkey
Member
Offline
Activity: 105
Merit: 10
|
|
August 10, 2014, 02:23:04 PM |
|
I would think that once the XC app is released for mobile devices, the issue with sending/receiving private transactions on restricted networks would be a non-issue. 3G, 4G, etc. are non-biased  |
|
|
|
|
|
Thrash
|
|
August 10, 2014, 02:32:15 PM |
|
Ok now, someone hook me up with the paperwallet info please I wanna do some experimenting.
I don't think there is a link to it yet. I sent it to the team for review earlier this week, but I'm sure they are busy. Hopefully we will hear something soon. Laredo7mm sent it to me and I have passed it on. I am traveling this weekend and will be back on Tuesday. Will follow up on it then. |
|
|
|
|
|
Youghoor
|
|
August 10, 2014, 02:34:32 PM |
|
Some of you raised some suggestions for the store so we decided to accept litecoin and bitcoin.
well now that is a good step |
|
|
|
|
|
|
|
SushiChef
|
|
August 10, 2014, 03:20:19 PM |
|
Did I really found the love of my life? |
|
|
|
|
|
akula999
|
|
August 10, 2014, 03:31:23 PM |
|
If anyone is interested, i'm selling my domain XCDESK.COM
I was originally going to use it, but found my personal life way to hectic to continue.
If you're interested PM/Let me know. Make me an offer.
|
Bitcoin: 1FzZehkiwfeeUmfmBrym8VvXX7gUj3miHe
XMR: 4AqrzGPfEKeZrVXyPDNXUrNeKZZGNYiXMDoY49PvdffKNTRg6xp2Qz74SZ72gT5F9HH8Vaic99ndRg6 UBGcVijaNStQjwwf
|
|
|
|
KimmyF
|
|
August 10, 2014, 03:39:17 PM |
|
And stealt addresses are comming:)
Great addition layer for anon but ....
If I pay someone anon. And not even the chain shows the coin's received how do you settle discussions between buyer and sender? What if that "whatever" seller claims they never received my payment?
|
|
|
|
|
synechist
Legendary
Offline
Activity: 1190
Merit: 1000
To commodify ethicality is to ethicise the market
|
|
August 10, 2014, 04:10:37 PM |
|
And stealt addresses are comming:)
Great addition layer for anon but ....
If I pay someone anon. And not even the chain shows the coin's received how do you settle discussions between buyer and sender? What if that "whatever" seller claims they never received my payment?
Simply speaking, you can't verify anything with 100% anonymity. This makes sense though. I mean, if you want to verify something (trustlessly) then you have to make information public. If it's public it's not anonymous. My guess is that single-use publicly known addresses are the sorts of things that retailers will need to use. Stealth addresses are no good for both seller and buyer, since there's (generally) a mutual interest in payment confirmation or tracking. Ultimately the flexibility that XC will offer with its privacy solution will be something like: - separate control over disclosing amounts and addresses - either amounts or addresses (or both) can be made public, private, or known only to sender and receiver. This way we'll be able to provide appropriate solutions to any given use-case. |
Co-Founder, the Blocknet
|
|
|
|
CryptoGretzky
|
|
August 10, 2014, 04:31:38 PM |
|
And stealt addresses are comming:)
Great addition layer for anon but ....
If I pay someone anon. And not even the chain shows the coin's received how do you settle discussions between buyer and sender? What if that "whatever" seller claims they never received my payment?
Simply speaking, you can't verify anything with 100% anonymity. This makes sense though. I mean, if you want to verify something (trustlessly) then you have to make information public. If it's public it's not anonymous. My guess is that single-use publicly known addresses are the sorts of things that retailers will need to use. Stealth addresses are no good for both seller and buyer, since there's (generally) a mutual interest in payment confirmation or tracking. Ultimately the flexibility that XC will offer with its privacy solution will be something like: - separate control over disclosing amounts and addresses - either amounts or addresses (or both) can be made public, private, or known only to sender and receiver. This way we'll be able to provide appropriate solutions to any given use-case. If you MUST track it and still wants it to be anonymous, it's quite straightforward with XC. You just need to take some additional steps. 1. Receiver: Generate a new public address 2. Sender: Using XChat gets public address from receiver 3. Sender: Use private transaction to send to another address that sender owns to anonymize his coins 4. Sender: Use those anonymized coins to send to receiver public address. (This is the public transaction on the blockchain that can be used to verify transaction) 5. Receiver (optional): Send the coins received using private transaction to another address of his choice. So, you can have best of both world with XC. |
|
|
|
zythos
Newbie
Offline
Activity: 48
Merit: 0
|
|
August 10, 2014, 05:12:22 PM |
|
Hi guys  . Don't know if this would be interesting in anyway for XCurrency, but thought i would link it anyway. [ANN] [ATM] TRANSFAIR crowdfund EUROPE TWO-WAY ATMs for 10 ALTCOINS https://bitcointalk.org/index.php?topic=694691.0. |
|
|
|
|
|
Queeq
|
|
August 10, 2014, 05:15:45 PM |
|
If you MUST track it and still wants it to be anonymous, it's quite straightforward with XC. You just need to take some additional steps.
1. Receiver: Generate a new public address
2. Sender: Using XChat gets public address from receiver
3. Sender: Use private transaction to send to another address that sender owns to anonymize his coins
4. Sender: Use those anonymized coins to send to receiver public address. (This is the public transaction on the blockchain that can be used to verify transaction)
5. Receiver (optional): Send the coins received using private transaction to another address of his choice.
So, you can have best of both world with XC.
You don't need step #4 if in step #3 you send directly to the generated address. You can still see in the blockchain, I assume, that coins arrived there even though the transaction is private. You just can't track source. Also #2 is not usually necessary. |
|
|
|
|
|
CryptoGretzky
|
|
August 10, 2014, 05:25:42 PM |
|
If you MUST track it and still wants it to be anonymous, it's quite straightforward with XC. You just need to take some additional steps.
1. Receiver: Generate a new public address
2. Sender: Using XChat gets public address from receiver
3. Sender: Use private transaction to send to another address that sender owns to anonymize his coins
4. Sender: Use those anonymized coins to send to receiver public address. (This is the public transaction on the blockchain that can be used to verify transaction)
5. Receiver (optional): Send the coins received using private transaction to another address of his choice.
So, you can have best of both world with XC.
You don't need step #4 if in step #3 you send directly to the generated address. You can still see in the blockchain, I assume, that coins arrived there even though the transaction is private. You just can't track source. Also #2 is not usually necessary. With stealth address, you need these steps. That's the whole point of the initial question of "how do you track and confirm a stealth transaction if the sender don't even know where the coins got sent to". Step #4 can be shifted to the receiver side if you want. I guess the option is here for either the sender/receiver to do that anonymizing from the public blockchain, but the steps is not optional for both sides. |
|
|
|
|
Queeq
|
|
August 10, 2014, 05:34:26 PM |
|
With stealth address, you need these steps. That's the whole point of the initial question of "how do you track and confirm a stealth transaction if the sender don't even know where the coins got sent to".
Step #4 can be shifted to the receiver side if you want. I guess the option is here for either the sender/receiver to do that anonymizing from the public blockchain, but the steps is not optional for both sides.
Well, there must be some other way to verify that coins arrived to the stealth address, otherwise it's inconvenient to do so many steps. I think special acknowledgement mechanism could be built into the protocol. |
|
|
|
|
|
CryptoGretzky
|
|
August 10, 2014, 05:38:03 PM |
|
With stealth address, you need these steps. That's the whole point of the initial question of "how do you track and confirm a stealth transaction if the sender don't even know where the coins got sent to".
Step #4 can be shifted to the receiver side if you want. I guess the option is here for either the sender/receiver to do that anonymizing from the public blockchain, but the steps is not optional for both sides.
Well, there must be some other way to verify that coins arrived to the stealth address, otherwise it's inconvenient to do so many steps. I think special acknowledgement mechanism could be built into the protocol. My solution is only based on the current parameters that we have been revealed to so far. We don't even know how stealth transaction exactly work yet. Maybe when it's released, there is already a confirmation system in place. So, these are all just assumptions. I have faith that Dan and team will deliver us a really great stealth solution. |
|
|
|
|
battbot
|
|
August 10, 2014, 06:00:09 PM |
|
|
|
|
|
|
|
