.... I can´t belive that we still have sell orders. 
Dev you are the guy, Thanks for the great new.
Topic: [ANN] CRAVE 1st POS Masternodes | Dark Assets | I2P | Market =Embrace The Dark= - page 133. (Read 826716 times)
April 24, 2015, 10:50:47 PM
Long time no following the market, things look better each day in crave ... I2P will be a wonderful integration for anon, multisig is the key of market .... I can´t belive that we still have sell orders.
Dev you are the guy, Thanks for the great new.
.... I can´t belive that we still have sell orders. Dev you are the guy, Thanks for the great new.
April 24, 2015, 10:39:48 PM
i was looking at i2p stuff from a few hero members, heres what one smart guy had to say
1.2
Differences to TOR
The main characteristic in which I2P differs from TOR is the focus of the project.
While TOR was designed with the intention to enable anonymous internet brows-
ing, I2P’s focus is to provide an anonymous network, isolated inside the internet,
offering various protocols and applications within. It is however possible to utilize
I2P outproxies to reach the internet and thus enable anonymous web browsing.
Another difference to the TOR network is, that I2P tunnels can only be used unidirectional compared to TOR’s bidi-
rectional tunnels. Also, as mentioned in Section 1.1 I2P uses garlic encryption
where TOR uses onion encryption. Both implementations are based on layered
encryption, garlic encryption offering the possibility to store multiple messages
inside the innermost layer [3].
http://userpage.fu-berlin.de/~semu/docs/2011_seminar_ehlert_i2p.pdf - must read
1.2
Differences to TOR
The main characteristic in which I2P differs from TOR is the focus of the project.
While TOR was designed with the intention to enable anonymous internet brows-
ing, I2P’s focus is to provide an anonymous network, isolated inside the internet,
offering various protocols and applications within. It is however possible to utilize
I2P outproxies to reach the internet and thus enable anonymous web browsing.
Another difference to the TOR network is, that I2P tunnels can only be used unidirectional compared to TOR’s bidi-
rectional tunnels. Also, as mentioned in Section 1.1 I2P uses garlic encryption
where TOR uses onion encryption. Both implementations are based on layered
encryption, garlic encryption offering the possibility to store multiple messages
inside the innermost layer [3].
http://userpage.fu-berlin.de/~semu/docs/2011_seminar_ehlert_i2p.pdf - must read
April 24, 2015, 10:35:04 PM
Almost done with the native I2P integration 
I updated the code for the latest secp256k1 and will get that checked in soon as well. 
I updated the code for the latest secp256k1 and will get that checked in soon as well. right on, sounds interesting... is that for the market integration? lol I'm not a techie so it sounds like latin to me
i2p is an anon network supposedly much safer than tor network.
Some coins are trying to implement native i2p integration for months, but without success
Anoncoin's Github readme https://github.com/Anoncoin/anoncoin states: "Anonymity: Native support of the I2P and Tor darknets, Zerocoin in development"
native support could mean like ICM originally said about crave, which was pointed out that it may be possible but it would be to hard to do reliably without some system in place. Im not familiar with what anoncoins i2p integration level is..
so looks like Crave may or may not be a first depending on if anoncoins is reliable. either way its a damn big obstacle and sounds more useful than tor. also if ICM implements useful i2p maybe we could see another round of SHA clonecoins pop up, or at the very least a bunch of "updates"
Lastly, implemening the i2p could make large steps forward on parts of the roadmap revolving around "E2E Messaging: G-Spot" as i2p is end to end encrypted. opening tunnels between clients over i2p could be a very secure solution to in wallet or in urge market messaging.
April 24, 2015, 10:33:20 PM
i hear that I2P has ability for different service communications inside its anonymous network 
April 24, 2015, 10:17:10 PM
Almost done with the native I2P integration I updated the code for the latest secp256k1 and will get that checked in soon as well.
I updated the code for the latest secp256k1 and will get that checked in soon as well. right on, sounds interesting... is that for the market integration? lol I'm not a techie so it sounds like latin to me
i2p is an anon network supposedly much safer than tor network.
Some coins are trying to implement native i2p integration for months, but without success
April 24, 2015, 10:14:17 PM
Almost done with the native I2P integration I updated the code for the latest secp256k1 and will get that checked in soon as well.
I updated the code for the latest secp256k1 and will get that checked in soon as well. HOLY SHIT!
Hell yeaah, If multi-sig escrow workflow is the key for the market, humm...market must be close to release
.... Hey dumpers, thanks for your cheap coins, I am a happy bagholder. April 24, 2015, 10:03:12 PM
Almost done with the native I2P integration I updated the code for the latest secp256k1 and will get that checked in soon as well.
I updated the code for the latest secp256k1 and will get that checked in soon as well. HOLY SHIT!
April 24, 2015, 09:45:03 PM
Might be no more cheap master nodes soon
April 24, 2015, 09:44:59 PM
Almost done with the native I2P integration I updated the code for the latest secp256k1 and will get that checked in soon as well.
I updated the code for the latest secp256k1 and will get that checked in soon as well. right on, sounds interesting... is that for the market integration? lol I'm not a techie so it sounds like latin to me
DEV WORKING
April 24, 2015, 09:41:14 PM
GO CRAVE GO GO GO
THE NUMBER 1
THE NUMBER 1
April 24, 2015, 09:25:33 PM
Almost done with the native I2P integration I updated the code for the latest secp256k1 and will get that checked in soon as well.
I updated the code for the latest secp256k1 and will get that checked in soon as well. right on, sounds interesting... is that for the market integration? lol I'm not a techie so it sounds like latin to me
April 24, 2015, 09:17:44 PM
Yeah... just like I said you copied it into it.
From your page:
Quote
COPY /b blk0001.dat+blk0002.dat bootstrap.dat
That isn't linearized, and has the original orphans in it.
run tail -f debug.log when importing and I can see the orphans.
You need to do this:
https://github.com/bitcoin/bitcoin/tree/master/contrib/linearize
Then show me the bootstrap.dat from that
April 24, 2015, 09:16:12 PM
Almost done with the native I2P integration I updated the code for the latest secp256k1 and will get that checked in soon as well.
I updated the code for the latest secp256k1 and will get that checked in soon as well. That's awesome.. I hope you could look at the linearize-data.py I pm'd you about ... when / if you get time
April 24, 2015, 09:15:21 PM
Is that linearized... or you just copied/renamed blk0001.dat into it? In other words does it have all the orphans... ?
bootstrap.dat with orphans won't import for me past certain blocks.
Edit: meh .. 30.5 MB size ... its got all the orphans.
addnode=104.238.174.13
addnode=107.191.46.130
and with version v1.4.2.0-g32a928e
no copy and rename test it out pls
So which linearize script did you use? Could I please see it?
April 24, 2015, 09:14:47 PM
Almost done with the native I2P integration I updated the code for the latest secp256k1 and will get that checked in soon as well.
I updated the code for the latest secp256k1 and will get that checked in soon as well. right on, sounds interesting... is that for the market integration? lol I'm not a techie so it sounds like latin to me
April 24, 2015, 09:13:37 PM
Is that linearized... or you just copied/renamed blk0001.dat into it? In other words does it have all the orphans... ?
bootstrap.dat with orphans won't import for me past certain blocks.
Edit: meh .. 30.5 MB size ... its got all the orphans.
addnode=104.238.174.13
addnode=107.191.46.130
and with version v1.4.2.0-g32a928e
no copy and rename test it out pls
So which linearize script did you use? Could I please see it?
April 24, 2015, 09:10:28 PM
Almost done with the native I2P integration I updated the code for the latest secp256k1 and will get that checked in soon as well.
I updated the code for the latest secp256k1 and will get that checked in soon as well. 
April 24, 2015, 09:08:49 PM
Is that linearized... or you just copied/renamed blk0001.dat into it? In other words does it have all the orphans... ?
bootstrap.dat with orphans won't import for me past certain blocks.
Edit: meh .. 30.5 MB size ... its got all the orphans.
addnode=104.238.174.13
addnode=107.191.46.130
addnode=144.76.238.2
addnode=174.58.206.96
addnode=185.92.221.84
addnode=188.115.173.17
addnode=188.40.96.57
addnode=199.188.182.127
addnode=24.42.7.194
addnode=45.63.6.112
addnode=45.63.84.183
addnode=46.101.182.210
addnode=46.101.183.139
addnode=46.101.183.141
addnode=54.149.240.82
addnode=69.119.232.175
addnode=70.67.68.166
addnode=83.157.62.179
addnode=83.99.112.200
addnode=84.168.115.51
addnode=84.250.30.132
addnode=85.214.22.190
addnode=85.25.223.7
addnode=89.3.213.211
addnode=97.94.120.12
addnode=98.214.222.61
and with version v1.4.2.0-g32a928e
no copy and rename test it out pls
April 24, 2015, 08:56:27 PM
Almost done with the native I2P integration I updated the code for the latest secp256k1 and will get that checked in soon as well.
I updated the code for the latest secp256k1 and will get that checked in soon as well. April 24, 2015, 08:40:34 PM
Is that linearized... or you just copied/renamed blk0001.dat into it? In other words does it have all the orphans... ?
bootstrap.dat with orphans won't import for me past certain blocks.
Edit: meh .. 30.5 MB size ... its got all the orphans.
Jump to: