[ANN] NeosCoin [NEOS] - with Arbitrush, Multi-Algo, In-wallet trading & More - page 24.

ereborltc

hero member

Activity: 966

Merit: 500

Quote from: twoturtles on August 21, 2014, 11:49:54 PM

Hey folks,

Here is the screencast of a fresh install working on Linux and the process to make it do so: https://www.youtube.com/watch?v=QwBZx2bH-wY

Back to work,

syntaks

ereborltc

hero member

Activity: 966

Merit: 500

Quote from: twoturtles on August 22, 2014, 03:32:26 AM

Quote from: twoturtles on August 21, 2014, 12:05:13 AM

Quote from: socket on August 20, 2014, 11:59:20 PM

Quote from: twoturtles on August 20, 2014, 11:46:59 PM

Quote from: socket on August 20, 2014, 11:40:12 PM

Quote from: twoturtles on August 20, 2014, 11:29:37 PM

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

cyberhacker

legendary

Activity: 1330

Merit: 1000

Quote from: Mrboot on August 22, 2014, 05:08:19 AM

Quote from: hoks on August 22, 2014, 05:05:21 AM

Quote from: cyberhacker on August 22, 2014, 04:51:27 AM

Quote from: hoks on August 22, 2014, 04:36:41 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.

Mrboot

legendary

Activity: 1204

Merit: 1000

Quote from: hoks on August 22, 2014, 05:05:21 AM

Quote from: cyberhacker on August 22, 2014, 04:51:27 AM

Quote from: hoks on August 22, 2014, 04:36:41 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 !

hoks

member

Activity: 73

Merit: 10

Quote from: cyberhacker on August 22, 2014, 04:51:27 AM

Quote from: hoks on August 22, 2014, 04:36:41 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

cyberhacker

legendary

Activity: 1330

Merit: 1000

Quote from: hoks on August 22, 2014, 04:36:41 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

Activity: 73

Merit: 10

i suggest if price below the ICO , dev team will buy some coin back .

TiberiuC

sr. member

Activity: 311

Merit: 250

Quote from: gross on August 22, 2014, 01:20:28 AM

Quote from: Crypto_Junkee on August 21, 2014, 09:45:40 PM

I'm going to laugh at all those that dumped below the ICO because of FUD. When the wallet comes out.....hopefully by the end of the weekend, this thing will fly. Whales want you to dump, and that's what you're doing. Good luck in crypto, cause you'll need it.

Whale is DEV,nobody buy almost this shitcoin except himself .ICO has no real value (not Proof Of Wook is no electric cost),DEV dump all ICO coin to get small profit and go away, idiot investors only buy a promise Grin

Don't use blue when trying to FUD, red is better. People take blue as positive.

twoturtles

legendary

Activity: 1050

Merit: 1000

Quote from: younier on August 22, 2014, 03:58:34 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

younier

full member

Activity: 135

Merit: 100

Thanks for the hard work,dev,i'm holding my coins

youngmike

sr. member

Activity: 252

Merit: 250

Damn I missed this one Sad

sofu

legendary

Activity: 1890

Merit: 1085

Degenerate Crypto Gambler

The time of cheap Neos will be over soon. I'm hodling strong Wink

ereborltc

hero member

Activity: 966

Merit: 500

Quote from: twoturtles on August 22, 2014, 03: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

+1000000

ereborltc

hero member

Activity: 966

Merit: 500

Quote from: twoturtles on August 22, 2014, 03:32:26 AM

Quote from: twoturtles on August 21, 2014, 12:05:13 AM

Quote from: socket on August 20, 2014, 11:59:20 PM

Quote from: twoturtles on August 20, 2014, 11:46:59 PM

Quote from: socket on August 20, 2014, 11:40:12 PM

Quote from: twoturtles on August 20, 2014, 11:29:37 PM

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

twoturtles

legendary

Activity: 1050

Merit: 1000

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

twoturtles

legendary

Activity: 1050

Merit: 1000

Quote from: twoturtles on August 21, 2014, 12:05:13 AM

Quote from: socket on August 20, 2014, 11:59:20 PM

Quote from: twoturtles on August 20, 2014, 11:46:59 PM

Quote from: socket on August 20, 2014, 11:40:12 PM

Quote from: twoturtles on August 20, 2014, 11:29:37 PM

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

hero member

Activity: 966

Merit: 500

Quote from: twoturtles on August 22, 2014, 01:33:49 AM

The only time I've been referred to as a "whale" was when someone was admiring my 6'1 290lb girlish figure. The ICO coins are all kept on the exchange as there's nowhere to withdraw them to. On top of that, the only way to *get* coins is to buy them. As I showed in my first screencast, I'm not that wealthy.

Regards,

syntaks

hes a reg fudder ..ignor him , i know your swamped in work right now just focus Wink

your awesome!
+1

Mrboot

legendary

Activity: 1204

Merit: 1000

Guys listen,

Stop the fud and redicoulus question , the one that are selling are or people who bought high but cant wait till launch.
Cause there have been no mining done yet, If they wanna sell against a loss you cant blame the DEV. for sure.
It will only make the coin stronger to get away of the weak players.

Also the ICO will never been a scam , cause its done by bittrex if the dev. (twoturlte) can't deliver he not getting the ICO ,
Also he doesnt desirve fud cause he is working hes butt off and is posting a lot of video's to prove hes progress.

So Just sit down and buy the coins cheap now cause at launch it will only go one way , so just enjoy it.

And for the people who doesnt know this dev. is not a scammer been around crypto's for a while and worked on the back of some really awesome coins, also a reason why people like Richie from bittrex back him up.

So lets stop fuding Neos havent desirve it, it gonna be huge !!.

Kind regards,

EdvinZ

sr. member

Activity: 994

Merit: 260

Trolls are found only in profitable places

Grab message Wink

twoturtles

legendary

Activity: 1050

Merit: 1000

The only time I've been referred to as a "whale" was when someone was admiring my 6'1 290lb girlish figure. The ICO coins are all kept on the exchange as there's nowhere to withdraw them to. On top of that, the only way to *get* coins is to buy them. As I showed in my first screencast, I'm not that wealthy.

Regards,

syntaks

Topic: [ANN] NeosCoin [NEOS] - with Arbitrush, Multi-Algo, In-wallet trading & More - page 24. (Read 94526 times)