twoturtles (OP)
Legendary
Offline
Activity: 1050
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 07:32:26 AM |
|
Yessir that's correct.
Are any steps taken to help obfuscate the final TX? Example: Bob sends Alice 166.32 NEOS via Arbitrush. Given timing and the unique amount sent. It would be trivial to discover Bob was the origin of the transaction if Alice receives 166.32 NEOS in a single output. As of right now the only obfuscation would be the timestamp as it purposely doesn't send it right away through to prevent matching up a certain send time/amount with another masked tx's. With PoT enabled it returns the one tx, but what I can do is modify it so that the amount sent is split up into fragments and just return an array of txids. Regards, syntaks I think that would help. Also, if you want to get fancy, I would consider further obfuscation. Like random amounts of uneven divisions sent at slightly differing times from different exit nodes if possible. That's exactly what came to mind when I was reading. It's literally now in my to-do. Thanks for the input Regards, syntaks As per your request, I've modified Arbitrush. When you send using it, the sent amount is fragmented, and the time at which it's sent is random within reason so as not to match up timestamps within the block chain and sequence of events. This combined with other transactions taking place using Arbitrush, will obfuscate on a much better level. The endpoint still receives the intended sum though. Best regards, syntaks
|
|
|
|
twoturtles (OP)
Legendary
Offline
Activity: 1050
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 07:36:38 AM |
|
Update:
1. Linux wallet is ready 2. Waiting on Windows build and OSX build from the other devs to move forward with the setup scripts
Regards,
syntaks
|
|
|
|
ereborltc
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 07:38:13 AM |
|
Yessir that's correct.
Are any steps taken to help obfuscate the final TX? Example: Bob sends Alice 166.32 NEOS via Arbitrush. Given timing and the unique amount sent. It would be trivial to discover Bob was the origin of the transaction if Alice receives 166.32 NEOS in a single output. As of right now the only obfuscation would be the timestamp as it purposely doesn't send it right away through to prevent matching up a certain send time/amount with another masked tx's. With PoT enabled it returns the one tx, but what I can do is modify it so that the amount sent is split up into fragments and just return an array of txids. Regards, syntaks I think that would help. Also, if you want to get fancy, I would consider further obfuscation. Like random amounts of uneven divisions sent at slightly differing times from different exit nodes if possible. That's exactly what came to mind when I was reading. It's literally now in my to-do. Thanks for the input Regards, syntaks As per your request, I've modified Arbitrush. When you send using it, the sent amount is fragmented, and the time at which it's sent is random within reason so as not to match up timestamps within the block chain and sequence of events. This combined with other transactions taking place using Arbitrush, will obfuscate on a much better level. The endpoint still receives the intended sum though. Best regards, syntaks been so much talk about all the other great features and all the fud that people forgot the beauty of this coin which is ARBITRUSH!! love the explanation of how it works and is improved... does this dev look like someone who doesn't know what he's doing?? your awesome turtle! keep it up like this and were gonna soar !! +1000000000
|
|
|
|
ereborltc
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 07:38:49 AM |
|
Update:
1. Linux wallet is ready 2. Waiting on Windows build and OSX build from the other devs to move forward with the setup scripts
Regards,
syntaks
+1000000
|
|
|
|
sofu
Legendary
Offline
Activity: 1890
Merit: 1085
Degenerate Crypto Gambler
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 07:53:40 AM |
|
The time of cheap Neos will be over soon. I'm hodling strong ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
|
youngmike
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 07:57:39 AM |
|
Damn I missed this one ![Sad](https://bitcointalk.org/Smileys/default/sad.gif)
|
|
|
|
younier
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 07:58:34 AM |
|
Thanks for the hard work,dev,i'm holding my coins
|
|
|
|
twoturtles (OP)
Legendary
Offline
Activity: 1050
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 08:01:54 AM |
|
Thanks for the hard work,dev,i'm holding my coins
My pleasure. I hope they're of good use to you and help you prosper at the same time. Regards, syntaks
|
|
|
|
TiberiuC
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 08:25:49 AM |
|
Don't use blue when trying to FUD, red is better. People take blue as positive.
|
|
|
|
hoks
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 73
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 08:36:41 AM |
|
i suggest if price below the ICO , dev team will buy some coin back .
|
|
|
|
cyberhacker
Legendary
Offline
Activity: 1330
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 08:51:27 AM |
|
i suggest if price below the ICO , dev team will buy some coin back .
if dev can not deliver all promises. bittrex will buy back. only buy low profits, sell low loses; nothing more.
|
|
|
|
hoks
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 73
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 09:05:21 AM |
|
i suggest if price below the ICO , dev team will buy some coin back .
if dev can not deliver all promises. bittrex will buy back. only buy low profits, sell low loses; nothing more. what i mean is dev should gave all investor the confidence , just like syscoin team ,they take almost 20% from IPO fund to buy coins from market
|
|
|
|
Mrboot
Legendary
Offline
Activity: 1204
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 09:08:19 AM |
|
i suggest if price below the ICO , dev team will buy some coin back .
if dev can not deliver all promises. bittrex will buy back. only buy low profits, sell low loses; nothing more. what i mean is dev should gave all investor the confidence , just like syscoin team ,they take almost 20% from IPO fund to buy coins from market Hes spending all hes time into makeing the coin awesome that cost money too you know life aint free !
|
|
|
|
cyberhacker
Legendary
Offline
Activity: 1330
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 09:11:38 AM |
|
i suggest if price below the ICO , dev team will buy some coin back .
if dev can not deliver all promises. bittrex will buy back. only buy low profits, sell low loses; nothing more. what i mean is dev should gave all investor the confidence , just like syscoin team ,they take almost 20% from IPO fund to buy coins from market Hes spending all hes time into makeing the coin awesome that cost money too you know life aint free ! dev is not controlling the raised btc now. give him time. this is actually no lose game. but ppl are selling under ICO.
|
|
|
|
ereborltc
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 09:27:15 AM |
|
Yessir that's correct.
Are any steps taken to help obfuscate the final TX? Example: Bob sends Alice 166.32 NEOS via Arbitrush. Given timing and the unique amount sent. It would be trivial to discover Bob was the origin of the transaction if Alice receives 166.32 NEOS in a single output. As of right now the only obfuscation would be the timestamp as it purposely doesn't send it right away through to prevent matching up a certain send time/amount with another masked tx's. With PoT enabled it returns the one tx, but what I can do is modify it so that the amount sent is split up into fragments and just return an array of txids. Regards, syntaks I think that would help. Also, if you want to get fancy, I would consider further obfuscation. Like random amounts of uneven divisions sent at slightly differing times from different exit nodes if possible. That's exactly what came to mind when I was reading. It's literally now in my to-do. Thanks for the input Regards, syntaks As per your request, I've modified Arbitrush. When you send using it, the sent amount is fragmented, and the time at which it's sent is random within reason so as not to match up timestamps within the block chain and sequence of events. This combined with other transactions taking place using Arbitrush, will obfuscate on a much better level. The endpoint still receives the intended sum though. Best regards, syntaks
|
|
|
|
|
ereborltc
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 09:27:55 AM |
|
i think POD would help
Just waiting on CryptoAsian to release it. He does POD's for free and he's swamped with tons of them so I'd cut 'em a break. I can't imagine it'd be too far off from now but I can't be certain of course. Regards, syntaks
|
|
|
|
ereborltc
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 09:28:41 AM |
|
Update:
1. Linux wallet is ready 2. Waiting on Windows build and OSX build from the other devs to move forward with the setup scripts
Regards,
syntaks
|
|
|
|
ereborltc
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 09:31:11 AM |
|
just reposted everything u need to know that twoturtles is working his ass off to get everything delivered way earlier than expected ... i think its time to give this man the respect he deserves right now.. very transparent and active!
great work! A++
|
|
|
|
studio1one
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 22, 2014, 09:37:49 AM |
|
Nice, keep the solid work coming man. Well played so far.
|
BINTEX | | ● ● ● ● ● ● ●
| | | | ● ● ● ● ● ● ●
| | Powered by,
|
|
|
|
|