Rotating Proxy Access 3200 IPs and Auto-Switching

localbitcoins.com removed my post with suggestions to improve their security

localbitcoins.com removed my post with suggestions to improve their security
Localbitcoins recently behaving like middle aged colonial rulers. They want to throttle user's voice. Recently my 3 tier verified account with 3000+ trades was hacked and my 1.47+ bitcoin was stolen from their wallet. They still didn't return my account to me. I found the flaws in their system and post some suggestions. But they removed my post. what they want actually? They only count profit and not look at the user's security.
https://preview.redd.it/pght7k5b7df51.jpg?width=1625&format=pjpg&auto=webp&s=dacfee97e8ac7bb5cb64c1e851aa0af654d11a51
The original post is as follows, whats your say?

With reference from these post: https://www.reddit.com/Bitcoin/comments/i1qyn1/authy_cost_me_33k_usd_in_10_min/?sort=new
and
https://www.reddit.com/localbitcoins/comments/i1hy26/localbitcoins_why_you_not_understand_emergency/
I want to ask localbitcoins to implement SMS based 2fa. As I scammed $33k usd for the vulnerability of Authy, people should have choice of avoid it. For login , bitcoin release and bitcoin send option, user should have choice of the type of 2fa they want. Someone might choose sms for login, auth for release, sms for sending btc or another combination.
For "forgot password" option localbitcoins or any wallet should verify the action with sms 2fa. they should send sms to the verified phone with the account. If this was in place, i could have saved 1.47 btc with them.
For "changing email" option sms based 2fa also must be used. This way none without the verified phone can change email.
For both option above, system also can check some personal details like Identity Documents no: or date of birth etc.
Localbitcoins should also maintain an emergency contacts, At least 1 person monitoring the support request during off hours and if anything urgent, he/she should take action. For my case, if someone blocked my account as soon as i emailed them, i could have saved this huge loss.
There should be a "lock my account" option. Localbitcoins can automate this process with a specific email or sms only phone number. If someone from his verified email or phone number email or sms to that specific email or number, the system should automatically block the respective account.
Localbitcoins should also detect proxy/vpn users. And should never let to send bitcoin or start trade with a new proxy/vpn. I always use my account from the real ip of my resident country. Suddenly someone login from proxy/vpn or from other location and localbitcoins let them to drain my account is not acceptable.
So, please all user of localbitcoins raise your voice for these security measures in localbitcons. We keep our hard earned money with them and they can't only sleep and count profit. I will soon write these to consumer authorities.
submitted by traderforbtc to Bitcoin [link] [comments]

Security measures localbitcoins must have as a financial service

With reference from these post: https://www.reddit.com/Bitcoin/comments/i1qyn1/authy_cost_me_33k_usd_in_10_min/?sort=new
and
https://www.reddit.com/localbitcoins/comments/i1hy26/localbitcoins_why_you_not_understand_emergency/
I want to ask localbitcoins to implement SMS based 2fa. As I scammed $33k usd for the vulnerability of Authy, people should have choice of avoid it. For login , bitcoin release and bitcoin send option, user should have choice of the type of 2fa they want. Someone might choose sms for login, auth for release, sms for sending btc or another combination.
For "forgot password" option localbitcoins or any wallet should verify the action with sms 2fa. they should send sms to the verified phone with the account. If this was in place, i could have saved 1.47 btc with them.
For "changing email" option sms based 2fa also must be used. This way none without the verified phone can change email.
For both option above, system also can check some personal details like Identity Documents no: or date of birth etc.
Localbitcoins should also maintain an emergency contacts, At least 1 person monitoring the support request during off hours and if anything urgent, he/she should take action. For my case, if someone blocked my account as soon as i emailed them, i could have saved this huge loss.
There should be a "lock my account" option. Localbitcoins can automate this process with a specific email or sms only phone number. If someone from his verified email or phone number email or sms to that specific email or number, the system should automatically block the respective account.
Localbitcoins should also detect proxy/vpn users. And should never let to send bitcoin or start trade with a new proxy/vpn. I always use my account from the real ip of my resident country. Suddenly someone login from proxy/vpn or from other location and localbitcoins let them to drain my account is not acceptable.
So, please all user of localbitcoins raise your voice for these security measures in localbitcons. We keep our hard earned money with them and they can't only sleep and count profit. I will soon write these to consumer authorities.
submitted by Crazy-Effect9986 to u/Crazy-Effect9986 [link] [comments]

Help setting up Bitcoin Core node with Tor hidden service

I am trying to run a full node with Bitcoin Core and get it running as a Tor hidden service but the steps I am following are from many sources and I feel like I have been missing steps in between, not to mention that my technical skills are fairly basic.
Here's where I'm at (Windows):
Can someone please tell me if I've missed something or if I've done it right then how to check that I have?
Thanks!
Update: Currently I have a "work-around" by running tails in a VM and running bitcoin-qt inside that. Because it's a livecd if it gets shutdown for any reason I'd have to set it up each time so I would still like to get the full node running with Tor on Windows.
I am using bitcoin-qt.exe from the Windows installation of Bitcoin Core and using any combination of the network settings to get it to use Tor and it does connect to onion addresses, sometimes one or two and the remaining of the eight are normal nodes.
I can't figure out how to make Bitcoin Core only connect Tor nodes instead of none or a mixture.
Update 2: Instead of using the Tails in a VM workaround, I have the windows Bitcoin Core Node running properly over Tor now. I still have to wait a few days at least to see if I can get more than two incoming connections.
I read in many places that port 8333 had to be opened in order to receive incoming connections but I have been assured that doesn't apply to onion nodes and that checking getnetworkinfo with bitcoin-qt console shows onion as reachable is proof.
There was also an issue with Tor not working with the CookieAuth when that set was added to torrc. Simply CookieAuthFile needed to be added.
I'm adding these notes in case any other windows user has trouble getting their node running with Tor.
SYD4uo was a huge help and I appreciate those others that took the time to give advice. Cheers!
This was also very helpful
submitted by Slayer3608 to Bitcoin [link] [comments]

Logs of yesterday's dev meeting

 Dev meeting?  Would say so, yes  The people are still exhausted from the payment ID meeting :)  Guess we could ping some people  vtnerd, moneromooo, hyc, gingeropolous, TheCharlatan, sarang, suraeNoether, jtgrassie  Anyone up for a meeting?  Yep I'm here  Here  o/  Perhaps we should just start and people will eventually hop in?   oof   sorry guys, I'm working on the new FFS and I forgot all about this. Got a couple of new volunteers.   This literally might be able to launch tomorrow.  I know that. It's called "flow" :)  I could run if you're out of time?   go for it dEBRUYNE   you guys are going to like this new FFS. We're like 99% done.  Hi  rehrar: someone else do the milestone thing already?  All right, jtgrassie, perhaps you'd to start w/ briefly describing your most recent PR? https://github.com/monero-project/monero/pull/5091   oneiric, xiphon did everything   like....everything  As far as I can see, it allows the user to push his transaction over I2P, thereby masking the origin IP of the sendeuser  great  And it hooks into vtnerd's PR right?  Sure. It basically just builds on vtnerds Tor stuff.  sorry dEBRUYNE  Really not much added.  I have it running and tested.  From the perspective of the user, what needs to be configured exactly?  Nice  Assuming the PR is included in the release binaries  I'm using knacccs i2p-zero duirng testing but will of course work with any i2p setup   sorry dEBRUYNE <= Np  Looks a little like dams breaking, now that we have some dark clouds over Kovri and people take matters into their own hands ...  User needs to run i2p, expose a socks service and and inbound tunnel.  Basically same as Tor  Okay, so should be reasonable as long as we write proper documentation for it (e.g. an elaborate guide)  rbrunner, yes, knaccc credit for jumping on i2p-zero really  dEBRUYNE: documentation monero side is kindof done. i2p side is very much implementation specific.  I suppose we could write some guides for the most popular implementations?  e.g. i2p-zero aims to be zero conf, but i2pd or Kovri would be differnet.  I see, great  vtnerd___: Do you want to add anything?  could amend the current kovri guide for monero use from --exclusive-peer to the new proxy support  Now I have i2p-zero running and tested with the #5091, I plan to jump back over to helping knaccc on getting that polished.  I added support for socks proxy in the basic wallets  ^ excellent  Yes vtnerd___ I havent tested it yet but looks sweet.  So connections to `monerod` over Toi2p are possible within wallet cli and wallet rpc  Awesome  This also implies auth+encryption even if ssl is not in use (when using an onion or i2p address)  All right  moneromooo: are you here? If so, could you perhaps share what you've been working on?  I am.  I revived the SSL PR, more stuff on multi sender txes, an implementation of ArticMine's new block size algorithm.  I presume a multi sender tx works similar to multisig insofar as the senders have to exchange data before the transaction can be performed right?  Yes.  There are 2 SSL PRs. What's the diff?  Theoretically this would also allow the sender to provide an output right? Which would be kind of similar to Bitcoin's P2EP  The second one adds some things like selecting a cert by fingerprint.  Yes.  (for the first sentence)  All right, awesome  For anyone reading, this breaks the assumption of the inputs belonging to a single sender, which makes analysis more difficult  Nice side-effect.  Much work coming for the various wallets to support that  rbrunner: Anything you'd like to share in the meeting btw?  Yes, just a little info  I have started to seriously investigate what it would mean to integrate Monero into OpenBazaar  I have already talked with 2 of their devs, was very interesting  In maybe 2 or 3 weeks I intend to write a report  Too early to tell much more :)  Soon^tm I guess :)  Yep  Currently wrestling with Go debugging  whole new world  moneromooo: Has pony recently shared any insights regarding the upcoming 0.14 release btw?  No.  All right  I would love to see the tor & i2p PR's merged sooner rather than later so we can get more testing done.  ^ +1  Isn't that famous early code freeze already on the horizon?  fluffypony, luigi1111 ^  I suppose I could provide a little update regarding the GUI btw  As always, lots of bug fixes and improvements :-P  selsta has recently added a feature to support multi accounts  dsc_ has revamped the wizard and will now start working on implementing the different modes and a white theme  dsc_ is working fulltime on the GUI already?  yes  :)   dsc_ is bae  In light of the recent payment ID discussion, we've also, by default, disabled the option to add a payment ID unless the user explicitely activates the option on the settings page  rehrar ^  nice   I spoke about this yesterday at the coffee chat, this is not a good decision.  How does it handle integrated addresses? The same way?  rehrar ?   For the next many months, we are still stuck with PAyment IDs in the ecosystem. Making it harder for people to access them will make Monero suck so hard to use for the average person for many months.  i agree with rehrar   Remove the option of Payment IDs when we remove Payment IDs  rehrar: The new GUI release won't be live until probably mid march though  Which is a few weeks in advance of the scheduled protocol upgrade   Payment ID removal comes in October   right, but Payment IDs are not removed in March  Did we not have loose consensus on removing the old, unencrypted payment IDs in march?   they are removed in October  We had discussed a deprecation in March  and a ban in October   ok, then if we are going to do that, we have to commit to it and contact the exchanges like Binance that use them and get rid of them in the next few months  (of unencrypted)   Binance is huge, and if they still use them, then people will be very upset that they can't deposit or use Payment IDs easily   I'm just speaking from a UX perspective.  I thought it was unencrypted in April and possibly encrypted in October  Yes I do agree  Timeline and notes: https://github.com/monero-project/meta/issues/299  impossible to remove them for march, many exchanges still use them  We can defer it to the 0.15 release if needed  Well, that wasn't the impression for them log that I just read today  This was all discussed in the earlier meeting linked above   We have to force the ecosystem off of Payment IDs before we remove them from the UI, is all I'm saying  Remove != make difficult to use  ... or make them more difficult there, right?  ping sgp_   sarang, I understand, and I agreed with you during that meeting. But then I started thinking of it as a UX person, which I am.   And that huge massive problem leapt out at me  i think making them difficult to generate is a good idea but making them difficult to consume and use is a bad idea  well, maybe not a good idea, but a better idea   ^  If we defer the decision to depriciate long payment IDs to october, won't we have the same issue then?  The UI can gave an expandable payment ID field like MyMonero and we can still call it deprecated   It is foolhardy to remove an option that the ecosystem uses. So I suggest we keep the Payment ID in the UI until October when they are completely banned.   no dEBRYUNE, because they will be banned via consensus  sgp_ imo it may be a misdirection of dev resources to add that since things are proceeding in the short term rather than long term  but this is a relatively minor point  Nothing matters til exchanges change  All right   The issue is that consensus will still have them in April, and exchanges won't upgrade because they are still allowed. Thus they must still be in the UI.  endogenic these changes are already merged in the GUI to hide it like you do  ok   But when they are banned, exchanges are forced to upgrade or stop using Monero, so we can remove them safely because they won't be in use  rehrar: that's a strong assumption   sarang that they will upgrade?  yes   if they don't, then they can't use Monero  If exchanges require pid, users need a way to set a pid. Making it hard for the user in the interim is just going to be a nightmare.   we have decided to take our "stand" in October  A way that is not too hard, then  To be clear, we still intend to deprecate long encrypted payment IDs in April right? But no enforcement until October   the term "deprecated" doesn't mean much if it's still allowed, and used in popular places   yes, as far as I understand it   jtgrassie, exactly  True I suppose  dEBRUYNE: we need to be more specific when talking about deprecation   the person who suffers is the user  There are two proposals for GUI deprecation:  1. Hide it in the send screen with a simple option to expand (currently merged iirc)  2. Hide it completely in the send screen unless users enable the field in advanced settings (PR'd but not merged yet iirc)  What are the arguments for 2?   Both are poor options, but 1 is better than 2 by a long shot   Well the people who need to be made to "suffer" are the exchanges. And I don't see a way to make exchanges "suffer" other than by having their suffering customers complain to them constantly that they need to update.  ^  CLI has something similar where users need to set a manual payment ID transfer mode. Not sure if it's merged yet   the way to make the exchanges suffer is when we ban PIDs. They either upgrade or don't use Monero.  exact;y  Agree with rerahr here  have exchanges been provided with clear, practical, sufficient technical upgrade plans for supporting what they're doing with PIDs but with subaddrs?    Both are poor options, but 1 is better than 2 by a long shot <= I wouldn't call 1. a poor option. Have you actually checked how it looks?  Because it states "Payment ID" and a user has to click on the + to expand the field  endogenic: yes the email when out. Blog post coming soon, but contains the same info as the email  also the exhcnages' users are often using wallets that don't support subaddresses  ok great   as well, it should be noted that the timeline for exchanges to upgrade is September, not October when the fork is.  Which wallets are that?  Rehrar: I don't see option 1. causing any issues/confusion  i guess it doesnt matter too much if withdrawing as a personal user the main address should suffice   Because September is when the new versions will be coming out without PIDs in the UI  If there's opposition to 2, 1 is fine. We can still call it deprecated which is the optics we need anyway   exchange users are often just using other exchanges lol. No wallets involved.   dsc_ dEBRUYNE, ok, I trust you guys here then  rbrunner: i was thinking mymonero last i heard  Ok  pigeons: rbrunner yes receiving on subaddresses won't be supported yet  sending to them has been possible though  and yes as learnandlurkin says often they withdraw to other systems like exhcnages that also dont yet support subaddresses  I really can't come up with any good argument for 2. right now  endogenic: seems not much of an issue then. Exchanges will typically support withdrawals to both subaddresses and plain addresses (especially if we are going to force them to use subaddresses)  For deposits, MyMonero works properly if the user sends to a subaddress  Actually the second solution was already merged: https://github.com/monero-project/monero-gui/pull/1866  Maybe not enough eyes watching :)   The important thing is to have done something to justify having a big "DEPRECATED IN APRIL" stamp on PIDs to spook exchanges in the interim  This was for solution 1: https://github.com/monero-project/monero-gui/pull/1855   The Monero Community Workgroup will start making noise everywhere we can to exchanges, and everywhere else that will listen. Try to get on those garbage news sites also.   So everyone knows that deprecated in April, and banned in September  Hey, for solution 1, write "Payment ID (optional, deprecated)" or similar there  rbrunner: noted  rehrar: probably wait until the blog post, but it should only be a few days   Maybe a Reddit sticky post would be useful?   With the blog post   If people are over freaking out about the hashrate  or terabyte blockchain :)  sigh  Any questions for the MRL side?  Is someone checking ArticMine's block size changes for weird behaviour in some cases etc ?  How would such testing work? Private blockchain?  I'm waiting on cost information from ArticMine to complete the model  Or just simulations?  Also, smooth suggested a mean rather than median for the 100000 block op. It would indeed be much nicer if it doesn't make the change worse.  You mean computationally or what?  Nicer ? Yes.  no sorting needed for mean  I'll add a separate sim for that  Well, just nicer. Forger the much.  Forger the Much sounds like the formal name of a Lord of the Rings character  :)  To close the payment ID discussion, in essence, we agree that we shouldn't make it difficult for the user to add a payment ID right (until 0.15 is released)  ?  I don't. I did make it harder.  In the CLI, somewhat other story, I would say  than the GUI  People there are used to juggle with options and CL parameters  rehrar: I recommend opening another issue to reverse 1866 and we can gather feedback on it there  Sounds good, to me at least   Dudes, if I do a Jitsi stream right now to show the new FFS in action, would you guys be interested in watching it?  I'd watch it, if the meeting is formally done  sure  yeah, can I start one and record it?   I'll give it in like fifteen minutes   I'll let you all know, stand by  I have a question on tx_extra if no one else has anything to talk about  People have said you can put arbitrary data in there in whatever format you want as long as you're willing to pay for it. However, do you need to mine the transaction for it to be included? I didn't think nodes would block transactions with arbitrary tx_extra data  It'll be in nodes' txpool when you relay it. A wallet could see it before it's mined.  moneromooo: will it be mined though?  by others  Is it valid ?  assume it's otherwise valid  Does it have a high enough fee ?  assume it does yes  I ran into conflicting information here: https://monero.stackexchange.com/a/3627/42  Then it will probably be mined.  I once had the idea to put "my" MMS messages in there, looked at the code, and found no hard blocks for tx_extra data  That answer looks incorrect.  It is incorrect  If it will be mined, then that meets my assumption. There seems to be some misconception that people will not mine transactions with arbitrary tx_extra. I can add some comments there  And please don't spam it, and don't put fingerprintable stuff in it. It's meant to be here for *useful* stuff that's "uniform" enough.  It will be mined, whether a wallet *displays* the tx_extra is a different question.  I don't think any wallet currently displays that  it soes if its a pid  I think  Yeah, of course :)  Great, that answers my question 
submitted by dEBRUYNE_1 to Monero [link] [comments]

My growing collection of info about NEO Vol. 2

It can be very time consuming to keep up to date on a single blockchain. If you just heard about NEO a few weeks ago it would be impossible catch up on past occurrences. I’m going to try and simplify the past, present and future as much as I can into one well thought-out post.
 
I made the first Volume around 6 weeks ago
https://www.reddit.com/CryptoCurrency/comments/75mul5/my_growing_collection_of_info_about_neo/
 
I felt it was time for an update since so much has happened.
If you want the up to date version in between Vol updates visit NEO and its located on the #3 top post of all time.
[Note: This Post is at max characters (40,000), some information will be left out]
 
https://imgur.com/a/NBI7S (img for mobile backround)
 

NEO dApps / Partnerships / ICO's

https://neo.org/dapps
 
Red Pulse $RPX (ICO Completed)
A next generation intelligence and content ecosystem for China markets
https://coin.red-pulse.com/
 
Neon Exchange $NEX (Upcoming ICO on NEO) (strategic collaboration with NEO)
NEX is a platform for complex decentralized cryptographic trade and payment service creation
https://twitter.com/neonexchange
https://neonexchange.org/
https://neonexchange.org/pdfs/whitepaper_v1.1.pdf
 
Elastos $ELA (strategic collaboration with NEO)
Blockchain Driven Internet
NEO will make itself compatible with Elastos, and Elastos will also support NEOVM, and allow the writing of smart contracts with established languages, such as C# and Java. Elastos will be an OS for the Blockchain, and NEO can help developers quickly create Blockchain applications. The combination of the two could connect different developers from around the world, forming a strong ecosystem for application development―all to better serve a Smart Economy.
http://www.elastos.org/
https://twitter.com/ElastosI
https://www.reddit.com/NEO/comments/6r1a6f/neo_and_elastos_reaching_strategic_collaboration/
 
Ontology $ONT (Partnership with NEO)
Ontology Network (ONT) is a blockchain/distributed ledger network which combines distributed identity verification, data exchange, data collaboration, procedure protocols, communities, attestation, and various industry-specific modules. Together this builds the infrastructure for a peer-to-peer trust network which is cross-chain, cross-system, cross-industry, cross-application, and cross-device.
 
NEO will be the primary digital assets service provider for clearing and settlement on Ontology. There is no contract between Ontology and NEO now, though Ontology and NEO already have an established partnership. One thing on the roadmap is that in the future business scenarios on Ontology want to hold ICOs they will be able to on NEO.
https://ont.io/#/home
https://www.reddit.com/NEO/comments/7f8bvb/ontology_network_ama_answers/
https://www.youtube.com/watch?v=lPWwcgpc3P0
https://twitter.com/OntologyNetwork?lang=en
https://imgur.com/a/Emo4Q
 
The Key $TKY (Upcoming ICO ) (strategic cooperation with NEO)
THEKEY is a Decentralized Ecosystem of Identity Verification Tool Using National Big-data and Blockchain. THEKEY team is now developing second generation on-line identify verification technology. NEO Smart Economy = Digital Asset + Smart Contract + Digital Identity, while digital identity is an indispensable element. With NEO technical support, the strategic corporation between THEKEY and NEO will provide better protection to your digital asset.
https://www.thekey.vip/
https://www.reddit.com/NEO/comments/7areac/ama_on_9th_nov_thekey_a_decentralized_ecosystem/
 
Qlink $QLC (Partnership with NEO) (Multi-chain) (Upcoming ICO on NEO)
World’s First Decentralized Mobile Network
Qlink, a decentralized mobile network, is dedicated to constructing an open-source telecom infrastructure on blockchain.
https://twitter.com/QlinkMobi
https://www.qlink.mobi/f/qlink
https://neonewstoday.com/general/qlink-partner-with-neo/
 
PeerAtlas $ATLAS (Upcoming ICO on NEO)
ATLAS: A Digital Token Supporting an Open-Source Medical Encyclopedia
http://www.peeratlas.com/
http://www.peeratlas.com/whitepaper.pdf
https://neonewstoday.com/interviews/peeratlas-q-a-colin-closse
 
High Performance Blockchain $HPB (ICO Completed)
HPB is a new blockchain architecture, positioned as an easy-to-use, highperformance blockchain platform. It aims to extend the performance of distributed applications to meet real world business needs. This is achieved by creating an architecture similar to an API operating system. The software architecture provides accounts, identity and authorization management, policy management, databases, and asynchronous communication on thousands of CPUs, FPGAs or clustered program schedulers. This blockchain is a new architecture that can support millions of transactions per second and support authorizations within seconds.
http://www.gxn.io/en.html
http://www.gxn.io/files/hpb_white_paper_en.pdf
https://www.allcoin.com/markets/HPB-BTC/0/
 
Aphelion $APH (ICO In Progress)
A Revolutionary Decentralized P2P Exchange Solution
https://aphelion.org/
https://aphelion.org/wp.html
https://github.com/Aphelion
 
Zeepin $ZPT (Crowd sale will start Jan 18, 2018) (Upcoming ICO on NEO)
The Distributed Creative New Economy.
Zeepin, a decentralized innovation community, is dedicated to promoting highly efficient circulation of innovation assets.
https://www.zeepin.io/
https://www.zeepin.io/Whitepaper_En_v1.0.pdf
https://github.com/zeepin
https://www.reddit.com/NEO/comments/7f94vs/ama_from_today_nov_24th_zeepin_the_distributed/
 
Stokit (Upcoming ICO on NEO)
Decentralized cloud storage
https://stokit.io/
Whitepaper release: 30th of November 2017
 
Universal Health Coin (Upcoming ICO on NEO )
http://www.universalhealthcoin.com/
 
AdEx (dApp built on NEO)
http://adex.network/
https://twitter.com/AdEx_Network/status/897529249661423616
 
 
Alphacat
More Information to come soon after Video is released from the Meetup
https://www.meetup.com/de-DE/Onchains-Blockchain-Project-Launch-NEO-Ecosystem-Sharing/events/245101761/
 
DeepBrain
More Information to come soon after Video is released from the Meetup
https://www.meetup.com/de-DE/Onchains-Blockchain-Project-Launch-NEO-Ecosystem-Sharing/events/245101761/
 
 

City of Zion (CoZ)

https://cityofzion.io/
https://medium.com/@cityofzion
https://medium.com/proof-of-working
https://steemit.com/@canesin
 
City of Zion (CoZ) is an independent group of open source developers, designers and translators formed to support the NEO BlockChain core and ecosystem.
CoZ primarily operates through the community Slack and CoZ Github, central places where the community shares knowledge and contributes to projects.
CoZ is neither a corporation, nor a consulting firm or a devshop / for-hire group.
Members
https://imgur.com/a/Gc9jT
CoZ aims to be low barrier of entry, the process is straightforward:
  1. Join the channel #develop.
  2. Fork or create a project.
  3. Publish as open source.
  4. After a couple of contributions a CoZ council member will invite you to the proper channel for your contributions.
  5. Receive rewards and back to 3.
Unit testing - Ongoing effort to implement code coverage for the core
Integration testing - Tools for automated testing, performance metrics and functionality validation on private test nets
Continuous integration - Automated multi-platform testing of all pull requests at GitHub.
Deployment pipeline - Automated tools and processes to ensure fast and reliable updates upon code changes
New C# implementation (NEO2) - Improve code quality, speed & testability
 
Roadmap
https://imgur.com/a/4CDhw
 
dApps competition
https://cityofzion.io/dapps/1
10 prizes of 1350 GAS, with 500 GAS to be used for smart contract deployment.
Deadline was the 16 of November 11:59 EST.
http://cityofzion.io/dapps/1 (Check out page to view websites / Githubs)
1st: NEO Smart IoT
2nd: imusify
3rd: Chain Line
4th: BlockAuth
5th: Phantasma
6th: NeoTrade
7th: Turing Complete Smart Contract
8th: KRYPTON
9th: Switcheo
10th: TripShares
https://drive.google.com/drive/folders/0B4wu5lNlukwybEstaEJMZ19kbjQ
 

NEO and Microsoft China Dev Competition

 

Competition Rules

  1. The competition will open on November 20, 2017 and close at 11:59 PM Beijing time (GMT+8), March 10, 2018. Please sign up and submit your work before the deadline.
  2. Participants are required to develop on the NEO blockchain. Please refer to github.com/neo-project and docs.neo.org for relevant codes and technical documents.
  3. During the competition, developers are free to collaborate and to submit their work as a team.
  4. Teams or individuals who fail to submit their work before 11:59 PM Beijing time (GMT+8), March 10, 2018 will not be eligible for prizes.
  5. Your submission must contain executable programs and codes.
 
$150,000 First prize(1 team)
$50,000 Second prize(2 teams)
$30,000 Third prize(3 teams)
$15,000 Award of merit(10 teams)
 
A judging panel made up of NEO founder Da Hongfei,NEO Founder & Core Developer Erik Zhang, CoZ founder Fabio, Elastos founder Chen Rong,ONT Founder Li Jun and experts from Microsoft China will select 16 winners out of all the contestants for a bounty pool worth a total of USD 490,000.
 
Total sign-ups :194 Data collected as of 2017/11/28
 
Country Sign-ups
China 48
USA 31
India 12
Norway 7
France 6
Other 90
 
https://neo.org/competition.html
 
 

ICO Firm

 
Projectico
A service that helps others launch a token sale if it is right for their cause and will be using NEO in most instances going forward. We have created a foundation that is bringing compliance and trust to the marketplace for ICOs and allowing international people to still participate.
https://www.projectico.io/
https://www.reddit.com/NEO/comments/7dd3s0/ama_on_20_nov_projectico_a_us_based_turnkey_token/
 
 

Key notes from the White Paper

http://docs.neo.org/en-us/
 
Digital Assets
Digital assets are programmable assets that exist in the form of electronic data. With blockchain technology, the digitization of assets can be decentralized, trustful, traceable, highly transparent, and free of intermediaries.
 
Digital Identity
Digital identity refers to the identity information of individuals, organizations, and other entities that exist in electronic form.
Our verification of identity when issuing or using digital identities includes the use of facial features, fingerprint, voice, SMS and other multi-factor authentication methods.
 
Smart Contracts
The NeoContract smart contract system is the biggest feature of the seamless integration of the existing developer ecosystem. Developers do not need to learn a new programming language but use C#, Java and other mainstream programming languages in their familiar IDE environments (Visual Studio, Eclipse, etc.) for smart contract development, debugging and compilation. NEO's Universal Lightweight Virtual Machine, NeoVM, has the advantages of high certainty, high concurrency, and high scalability. The NeoContract smart contract system will allow millions of developers around the world to quickly carry out the development of smart contracts.
 
Economic Model
NEO has two native tokens, NEOand NeoGas NEO represents the right to manage the network. Management rights include voting for bookkeeping, NEO network parameter changes, and so on. The minimum unit of NEO is 1 and tokens cannot be subdivided. GAS is the fuel token for the realization of NEO network resource control. The NEO network charges for the operation and storage of tokens and smart contracts, thereby creating economic incentives for bookkeepers and preventing the abuse of resources. The minimum unit of GAS is 0.00000001.
 
Distribution Mechanism
NEO's 100 million tokens are divided into two portions. The first portion is 50 million tokens distributed proportionally to supporters of NEO during the crowdfunding. This portion has been distributed.
The second portion is 50 million NEO managed by the NEO Council to support NEO's long-term development, operation and maintenance and ecosystem. The NEO in this portion has a lockout period of 1 year and is unlocked only after October 16, 2017. This portion will NOT enter the exchanges and is only for long-term support of NEO projects. The plans for it are as below:
▪ 10 million tokens (10% total) will be used to motivate NEO developers and members of the NEO Council
▪ 10 million tokens (10% total) will be used to motivate developers in the NEO ecosystem
▪ 15 million tokens (15% total) will be used to cross-invest in other block-chain projects, which are owned by the NEO Council and are used only for NEO projects
▪ 15 million (15% total) will be retained as contingency
▪ The annual use of NEO in principle shall NOT exceed 15 million tokens
 
GAS distribution
GAS is generated with each new block. The initial total amount of GAS is zero. With the increasing rate of new block generation, the total limit of 100 million GAS will be achieved in about 22 years. The interval between each block is about 15-20 seconds, and 2 million blocks are generated in about one year. According to this release curve, 16% of the GAS will be created in the first year, 52% of the GAS will be created in the first four years, and 80% of the GAS will be created in the first 12 years. GAS will be distributed proportionally in accordance with the NEO holding ratio, recorded in the corresponding addresses. NEO holders can initiate a claim transaction at any time and claim these GAS tokens at their holding addresses.
 
Consensus mechanism: dBFT
The dBFT is called the Delegated Byzantine Fault Tolerant, a Byzantine fault-tolerant consensus mechanism that enables large-scale participation in consensus through proxy voting. The holder of the NEO token can, by voting, pick the bookkeeper it supports. The selected group of bookkeepers, through BFT algorithm, reach a consensus and generate new blocks. Voting in the NEO network continues in real time, rather than in accordance with a fixed term.
 
Cross-chain assets exchange agreement
NeoX has been extended on existing double-stranded atomic assets exchange protocols to allow multiple participants to exchange assets across different chains and to ensure that all steps in the entire transaction process succeed or fail together. In order to achieve this function, we need to use NeoContract function to create a contract account for each participant. If other blockchains are not compatible with NeoContract, they can be compatible with NeoX as long as they can provide simple smart contract functionality.
 
Cross-chain distributed transaction protocol
Cross-chain distributed transactions mean that multiple steps of a transaction are scattered across different blockchains and that the consistency of the entire transaction is ensured. This is an extension of cross-chain assets exchange, extending the behavior of assets exchange into arbitrary behavior. In layman's terms, NeoX makes it possible for cross-chain smart contracts where a smart contract can perform different parts on multiple chains, either succeeding or reverting as a whole. This gives excellent possibilities for cross-chain collaborations and we are exploring cross-chain smart contract application scenarios.
 
Distributed Storage Protocol: NeoFS
NeoFS is a distributed storage protocol that utilizes Distributed Hash Table technology. NeoFS indexes the data through file content (Hash) rather than file path (URI). Large files will be divided into fixed-size data blocks that are distributed and stored in many different nodes
 
Anti-quantum cryptography mechanism: NeoQS
The emergence of quantum computers poses a major challenge to RSA and ECC-based cryptographic mechanisms. Quantum computers can solve the large number of decomposition problems (which RSA relies on) and the elliptic curve discrete logarithm (which ECC relies on) in a very short time. NeoQS (Quantum Safe) is a lattice-based cryptographic mechanism.
 

Reasons for choosing dBFT over PoW and PoS

 
With the phenomenal success of Bitcoin and its increasing mainstream adoption, the project’s unbounded appetite for energy grew accordingly. Today, the average Bitcoin transaction costs as much energy as powering 9.3 average American homes for 1 day.
https://digiconomist.net/bitcoin-energy-consumption#assumptions
This mind boggling amount of energy is not, as it is commonly believed, being wasted. It is put to good use: securing the Bitcoin network and rendering attacks on it infeasible. However, the cost of this security mechanism and its implications for an increasingly warming and resource hungry planet led almost the entire crypto industry to the understanding that an alternative has to be found, at least if we’re interested in seeing blockchain technology gaining overwhelming mainstream adoption.
The most popular alternative to PoW, used by most alternative cryptocurrency systems, is called Proof-of-Stake, or PoS. PoS is highly promising in the sense that it doesn’t require blockchain nodes to perform arduous, and otherwise useless, cryptographic tasks in order to render potential attacks costly and infeasible. Hence, this algorithm cuts the power requirements of PoS blockchains down to sane and manageable amounts, allowing them to be more scalable without guzzling up the planet's energy reserves.
As the name suggests, instead of requiring proof of cryptographic work, PoS requires blockchain nodes to proof stake in the currency itself. This means that in order for a blockchain node to be eligible for a verification reward, the node has to hold a certain amount of currency in the wallet associated with it. This way, in order to execute an attack, a malevolent node would have to acquire the majority of the existing coin supply, rendering attacks not only costly but also meaningless, since the attackers would primarily harm themselves.
PoS, as well as PoW, simply cause the blockchain to fork into two alternative versions if for some reason consensus breaks. In fact, most blockchains fork most of the time, only to converge back to a single source of truth a short while afterwards.
By many crypto enthusiasts, this obvious bug is very often regarded as a feature, allowing several versions of the truth to survive and compete for public adoption until a resolution is generated. This sounds nice in theory, but if we want to see blockchain technology seriously disrupt and/or augment the financial sector, this ever lurking possibility of the blockchain splitting into two alternative versions cannot be tolerated.
Furthermore, even the fastest PoS blockchains out there can accomodate a few hundred transactions per second, compare that to Visa’s 56,000 tx/s and the need for an alternative becomes clear as day.
A blockchain securing global stock markets does not have the privilege to fork into two alternative versions and just sit and wait it out until the market (or what’s left of it) declares a winner. What belongs to whom should be engraved in an immutable record, functioning as a single source of truth with no glitches permitted.
After investigating and studying the crypto industry and blockchain technologies for several years, we came to the conclusion that the delegated Byzantine Fault Tolerance alternative (or dBFT) is best suited for such a system. It provides swift transaction verification times, de-incentivises most attack vectors and upholds a single blockchain version with no risk of forks or alternative blockchain records emerging - regardless of how much computing power, or coins an attacker possesses.
The term Byzantine Fault Tolerance (BFT) derives its name from the Byzantine Generals problem in Game Theory and Computer Science, describing the problematic nature of achieving consensus in a distributed system with suboptimal communication between agents which do not necessarily trust each other.
The BFT algorithm arranges the relationship between blockchain nodes in such a way that the network becomes as good as resilient to the Byzantine Generals problem, and allows the system to remain consensus even if some nodes bare malicious intentions or simply malfunction.
To achieve this, Antshare’s version of the delegated BFT (or dBFT) algorithm acknowledges two kinds of players in the blockchain space: professional node operators, called bookkeeping nodes, who run nodes as a source of income, and users who are interested in accessing blockchain advantages. Theoretically, this differentiation does not exist in PoW and most PoS environments, practically, however, most Bitcoin users do not operate miners, which are mostly located in specialized venues run by professionals. At Antshares we understand the importance of this naturally occurring division of labor and use it to provide better security for our blockchain platform.
Accordingly, block verification is achieved through a consensus game held between specialized bookkeeping nodes, which are appointed by ordinary nodes through a form of delegated voting process. In every verification round one of the bookkeeping nodes is pseudo-randomly appointed to broadcast its version of the blockchain to the rest of the network. If ⅔ of the remaining nodes agree with this version, consensus is secured and the blockchain marches on. If less than ⅔ of the network agrees, a different node is appointed to broadcast its version of the truth to the rest of the system, and so forth until consensus is established.
In this way, successful system attacks are almost impossible to execute unless the overwhelming majority of the network is interested in committing financial suicide. Additionally, the system is fork proof, and at every given moment only one version of the truth exists. Without complicated cryptographic puzzles to solve, nodes operate much faster and are able to compete with centralized transaction methods.
https://www.econotimes.com/Blockchain-project-Antshares-explains-reasons-for-choosing-dBFT-over-PoW-and-PoS-659275
 

OnChain

 
It is important to note the technical difference between Onchain and NEO. Onchain is a private VC-backed company with over 40 employees. NEO is a public platform with different community-led groups contributing to this public project. There exists NEO council comprised of the original NEO creators, employees from Onchain, full time NEO council members and there is also the first Western based group called City of Zion.
Onchain, a Shanghai-based blockchain R&D company, first started developing Antshares in February of 2014 which will eventually become the foundation of DNA. Onchain was founded by CEO Da HongFei and CTO Erik Zhang in response to the attention from private companies garnered by the development of Antshares, China’s first public blockchain. In contrast to the weeks-old start-ups launching ICOs that is happening currently in the blockchain world, it took them 22 long months of R&D to even begin providing services to their first customers. Finally, in April 2016, the first whitepaper on consensus protocol from China was born — the dBFT (delegated Byzantine Fault Tolerance) protocol.
2016 was a busy year for Onchain and they really picked up the pace that year. Other than continuing the development of Antshares, brushing shoulders with Fortune 500 companies, Onchain became the first Chinese blockchain company to join Hyperledger — an open source blockchain project started by the Linux Foundation specifically focusing on the development of private and consortium chains for businesses.
In June of 2016, during the first of many future partnerships with Microsoft China, Onchain founded Legal Chain specifically targeting the inadequacies of the digital applications within the legal system. In 2005, (Digital Signature Act) was passed into national law which permitted an effective digital signatures to gain the same legal rights as a real signature.
In company with Microsoft China, they are also aiming to integrate the technology with Microsoft’s face and voice recognition API function to kick start this digital revolution within the legal system. At the same time, a partnership was formed with FaDaDa, a third-party platform for electronic contracts that has processed over 27 million contracts to date, to provide secure evidence storage with DNA. If that’s not enough, they were also voted as KPMG’s top 50 Fintech Company in China and established a relationship with the Japanese Ministry of Economy, Trade and Industry which led to the recent tour to Japan. Finally, at the end of 2016 they announced a partnership with Alibaba to provide attested email service for Ali Cloud with Legal Chain where it provides a proof-of-existence for a blockchain-powered email evidence repository for enterprise-level use.
Fosun Group, China’s largest private conglomerate, have recently invested into Onchain in order to apply DNA across all of its businesses. Currently, Fosun International has a market cap of 102.98 billion dollars on the Hong Kong Stock Exchange and that is only its international branch.
The role of Onchain so far is reminiscent of Ethereum’s EEA in addition to a stronger emphasis of governmental cooperation. Onchain has identified the shortcomings of present laser focus of hype on public platforms such as NEO and Ethereum and addressing that with DNA. DNA envisions a future where a network of assorted, specifically designed blockchains serving private enterprises, consortiums, government and the public communicating with each other forming an interconnected blockchain network.
This is the goal of DNA — infiltrating every little inefficient niche that had no better alternatives before the invention of blockchain. What is especially critical to remember during this explosive time of hype driven partly by the obscene degree of greed is that not every little niche that blockchain can fill will be holding its own little ICO. Some of those efficiencies gained will simply be consumed by companies privately or by public systems such as the legal system.
 
https://hackernoon.com/neo-onchain-and-its-ultimate-plan-dna-4c33e9b6bfaa
http://www.onchain.com/
https://github.com/DNAProject/DNA
https://siliconangle.com/blog/2016/10/20/onchain-partners-with-alibaba-for-blockchain-powered-email-evidence-repository/
https://www.reuters.com/article/us-fosun-blockchain/chinas-fosun-invests-in-local-version-of-bitcoin-tech-blockchain-idUSKCN1B30KM
 

Traveling

 
August 8th to August 12th
From August 8th to August 12th, 2017, the NEO core team, led by founder & CEO Da Hongfei will travel to Japan to explore the forefront of Japan's Blockchain innovation. This trip represents the first in a series of trips around the world with the goal to foster international cooperation's and to keep up with the fast pace in Blockchain innovation. Starting in Japan, the NEO core team will visit famous local Blockchain research institutions and active communities to engage in bilateral communication. NEO will meet with Japanese tech-celebrities to gain insights about the latest developments in the Japanese Blockchain and digital currency community. Additionally, Japanese local tech media will conduct an interview allowing NEO to present its development status and its latest technological innovations.
 
https://www.reddit.com/NEO/comments/6ry4s9/japan_the_neo_core_team_starts_out_on_an/
https://www.youtube.com/watch?v=SgTQ32CkxlU
https://www.reddit.com/NEO/comments/6ssfx1/neo_meetup_in_tokyo_august_10th_2017_2100h/
 
19th August, 2017
Blockchain X Series - NEO example applications
 
20th August, 2017
NEO and Microsoft Azure host a blockchain programming training in Shanghai
 
23rd August, 2017
INNOxNEO Blockchain Open Nights: 2nd Meeting
 
24th August, 2017
NEO Meetup in Taipei
 
13th September, 2017
INNOxNEO Blockchain Open Nights: 3rd Meeting
 
14th September, 2017
NEO Shanghai Meetup with NEO team
 
24th September, 2017
NEO Blockchain Programming Day - Hangzhou Station
 
27th September, 2017
INNOxNEO Blockchain Open Nights: 4th Meeting
 
27th September, 2017
First London NEO Developer Meetup!
 
4th October, 2017
First San Francisco NEO Developer Social!
 
14th-16th October, 2017
GNOME.Asia Summit 2017, Chongqing, China
 
21st October, 2017
NEO JOY, Exploring Blockchain application, Nanjing, China
 
26th October, 2017
Inaugural Global Fintech & Blockchain China Summit 2017
 
28th October, 2017
NEO meetup in Seoul, Korea:
 
28th October, 2017
NEO Blockchain Programming Day - Beijing Railway Station:
 
November 12th, 2017
NEO JOY in Hangzhou: Considerations on Basic Service Facilities in Blockchains:
 
November 18th - 19th, 2017
NEO attending China open source conference 2017:
 
November 21st, 2017
NEO attending swissnex China in Shanghai:
 
November 27th, 2017
ONCHAIN meetup NYC, Onchain's Blockchain Project Launch + NEO Ecosystem Sharing Session
 
November 27th, 2017
China&USA NEO blockchain meetup in Manhattan NYC
 
November 30th, 2017
Meetup San Francisco: The Future Of Blockchain With The Founders of NEO, Elastos, & Stellar
 
December 4th, 2017
NEO attending Blockchain World Conference in Bangkok:
 
December 7th, 2017
NEO meetup Singapore:
 
December 13th, 2017
NEO meetup at Cambridge:
 

Networks proves itself with the first ICO

 
ICOs, on other platforms such as Ethereum, often resulted in a sluggish network and transaction delays. While NEO’s dBFT consensus algorithm is designed to achieve consensus with higher efficency and greater network throughputt, no amount of theoretical calculations can simulate the reality of real-life conditions.
 

Key Observations

 
Smart Contract Invocations:
A total of 13,966 smart contracts invocations were executed on the NEO network over this time period, of which, nearly all called the RPX smart contract method mintTokens. A total of 543,348,500 RPX tokens were successfully minted and transferred to user accounts, totalling 10,097 smart contract executions.
 
Refunded Invocations:
A total of 4182 refund events were triggered by the smart contract method mintTokens. (Note: RPX has stated that these refunds will be processed within the next two weeks.)
 
Crowdsale Statistics:
A successful mintTokens execution used around 1043 VM operations, while an execution that resulted in a refund used 809 VM operations. Within the hour and six minutes that the token sale was active, a total of 12,296,409 VM operations were executed. A total of 9,575 unique addresses participated in the RPX ICO. Half of these, approximately 4,800 unique addresses, participated through CoZ’s Neon wallet. The top 3 blocks with the most transactions were block 1445025 (3,242 transactions), block 1444902 (2,951 transactions), and block 1444903 (1609 transactions).
 
Conclusion on Network Performance
At the moment, the consensus nodes for the NEO network are operated by the NEO Council in China. By Q1 2018, NEO Council aims to control less than two-thirds of the consensus nodes.
We are pleased to note that the NEO network continuted to operate efficiently with minimal network impact, even under extreme network events. Block generation time initially slowed down to 3 minutes to process the largest block, but quickly recovered to approximately 25 seconds. Throughout the entire RPX ICO, consensus nodes were able to achieve consensus and propagate new block transactions to the rest of the network. In closing, while we consider this performance to be excellent, NEO Council and City of Zion areworking closely together on upgrades, that will increase the throughputs of the NEO network.
 

Hyperledger

 
Members and governance of Hyperledger:
Early members of the initiative included blockchain ISVs, (Blockchain, ConsenSys, Digital Asset, R3, Onchain), well-known technology platform companies (Cisco, Fujitsu, Hitachi, IBM, Intel, NEC, NTT DATA, Red Hat, VMware), financial services firms (ABN AMRO, ANZ Bank, BNY Mellon, CLS Group, CME Group, the Depository Trust & Clearing Corporation (DTCC), Deutsche Börse Group, J.P. Morgan, State Street, SWIFT, Wells Fargo), Business Software companies like SAP, Systems integrators and others such as: (Accenture, Calastone, Credits, Guardtime, IntellectEU, Nxt Foundation, Symbiont).
The governing board of the Hyperledger Project consists of twenty members chaired by Blythe Masters, (CEO of Digital Asset), and a twelve-member Technical Steering Committee chaired by Christopher Ferris, CTO of Open Technology at IBM.
http://www.8btc.com/onchain-hyperledger
https://en.wikipedia.org/wiki/Hyperledger
 
“As a leading open-source contributor in China’s blockchain community, Onchain shares the same values as the Linux Foundation and the Hyperledger project intrinsically. We believe international collaboration plus local experience are key to the adoption of distributed ledger technology in China; we are also very excited to see other Chinese blockchain startups join Hyperledger and look forward to adding our combined expertise to the project.” Da Hongfei, Founder and CEO of Onchain
https://hyperledger.org/testimonials/onchain
 

Important Articles

 
Response to baseless FUD
https://medium.com/@MalcolmLerideresponse-to-baseless-fud-9b7e5e2eeeea
 
Distribution technology DNA framework went through the national block chain standard test On May 16th, the first China block chain development competition in Hangzhou announced that Onchain, became the first through the national standard test block system.
http://www.51cto.com/art/201705/539824.htm?mobile
 
Da Hongfei and OnChain working relationship with Chinese Government
https://finance.sina.cn/2017-04-13/detail-ifyeifqx5554606.d.html?from=wap
http://www.gz.chinanews.com/content/2017/05-28/73545.shtml
 
The Chinese government is reportedly preparing to allow the resumption of cryptocurrency trading in the country in the coming months, with the required anti-money laundering (AML) systems and licensing programs in place.
https://coingeek.com/cryptocurrency-trading-poised-to-make-a-return-in-china-report/
 
Japanese Ministry of Economy, Trade and Industry - Working with OnChain and NEO
http://www.8btc.com/onchain-ribenjingjichanyesheng
 
Notice NEO will be invited to attend the INNO x Austrade China-Australia chain high-end exchange
AUSTRADE - The Australian Trade and Investment Commission is the official government, education and investment promotion agency of the Australian Government
https://mp.weixin.qq.com/s/LmXnW7MtzOX_fqIo7diU9A
 
Source for NEO/OnChain Microsoft Cooperation:
http://www.8btc.com/onchain-microsoft
 

Da Hongfei quotes

 
"There is no direct cooperation between Alibaba and NEO/Onchain, other than their mailbox service is using Law Chain to provide attested email service. In terms of Microsoft, yes we have cooperation with Microsoft China because NEO is built with C# and .NET Core, and NeoContract is the first in the world to support writing smart contract with C#"
https://www.reddit.com/NEO/comments/6puffo/we_are_da_hongfei_and_erik_zhang_founders_of_neo/dksm5ga/
 
"We have pretty good communication with government, with regulators. They don't have any negative impression with NEO and they like our technology and the way we deal with things. Regulation is not an issue for us"
https://www.youtube.com/watch?v=qpUdTIQdjVE&feature=youtu.be&t=1m16s
 
“Before they started cleaning up the market, I was asked for information and suggestions” “I do not expect the government to call me in the short-term and say, ‘Let’s use NEO as the blockchain technology infrastructure of China.’ But in the medium term? Why not? I think it’s possible.”
https://medium.com/@TheCoinEconomy/neo-founder-da-hongfei-advised-china-on-ico-exchange-ban-says-govt-4631b9f7971
 

Upcoming Roadmap

 
Decentralization of consensus nodes
▪ P2P Network optimization – Network optimizations to ensure fast block generation after decentralization.
▪ Voting Algorithm Optimization – Adjustments in voting algorithm to prevent identified attack vectors.
▪ Candidate List Website – Published list of candidates so that voters know who they are voting for.
▪ NEO Council Consensus Node < 2/3 – NEO Council shall operate less than two thirds of consensus nodes by the end of quarter 1, 2018.
 
Our original plan was to start decentralize in Q1 2018. We are however growing faster than expected and cannot accept the risk with being as centralized as we currently are. The conclusion is that we re-prioritize and start the process of decentralizing today. We believe that NEO community groups and exchanges will be suitable to run consensus nodes; community groups already know the technology, and exchanges are already running full nodes with high uptime and monitoring. We welcome interested parties to reach out to us on [email protected]. A NEP to encourage voting will be presented in the coming weeks.
https://neo.org/blog/Details/3016
 
Universal Data Format for Wallet/Node Prog.
▪ NEP2 – Private Key Encryption/Decryption (2017Q4) - Method for encrypting and encoding a passphrase-protected private key.
▪ NEP3 – Universal Data Format (2017Q4) – Standard data format to allow easier wallet and node programming.
https://neo.org/en-us/blog/details/65
 
Promotion/Ecosystem
▪ Globally Legal Token-raising Framework (2017Q4) – Following government interest to regulate ICO’s, NEO will complete a framework to raise tokens legally in all major markets by the end of 2017.
▪ NEO DevCon 1 (2017Q4) – First NEO Development Conference! More details at later date.
▪ CoZ Funding (2017Q4) – Continuous funding plan for CoZ covering next 5 years.
▪ Seed Projects (2017Q4) – First seed projects to be cross-invested with the dedicated NEO pool.
https://neo.org/en-us/blog/details/65
 

NEO Github

https://github.com/neo-project
 
NEO Smart Economy https://github.com/neo-project/neo
1.2k Stars
383 Forks
327 commits
17 contributors
 
neo-gui https://github.com/neo-project/neo-gui
 
examples-csharp https://github.com/neo-project/examples-csharp
 
proposals https://github.com/neo-project/proposals
 
 

CityOfZion Github

https://github.com/CityOfZion
 
awesome-neo https://github.com/CityOfZion/awesome-neo
A curated list of awesome NEO libraries, applications and resources.
14 contributors
 
neon-wallet https://github.com/CityOfZion/neon-wallet
380 Stars
118 Forks
392 commits
29 contributors
 

DNAProject Github

https://github.com/DNAProject/DNA
 
NEO/GAS Donations welcome: ASdNxSa3E8bsxCE9KFKBMm3NA43sYJU9qZ
submitted by NEOcryptotrader to CryptoCurrency [link] [comments]

My growing collection of info about NEO

It can be very time consuming to keep up to date on a single blockchain. If you just heard about NEO a few weeks ago it would be impossible catch up on past occurrences. I’m going to try and simplify the past, present and future as much as I can into one well thought-out post.
[Note: This Post is at max characters (40,000), some information will be left out]
 
https://imgur.com/a/NBI7S (img for mobile backround)
 

NEO dApps / Partnerships / ICO's

https://neo.org/dapps
 
Red Pulse $RPX (ICO Completed)
A next generation intelligence and content ecosystem for China markets
https://coin.red-pulse.com/
 
Neon Exchange $NEX (Upcoming ICO on NEO) (strategic collaboration with NEO)
NEX is a platform for complex decentralized cryptographic trade and payment service creation
https://twitter.com/neonexchange
https://neonexchange.org/
https://neonexchange.org/pdfs/whitepaper_v1.1.pdf
 
Elastos $ELA (strategic collaboration with NEO)
Blockchain Driven Internet
NEO will make itself compatible with Elastos, and Elastos will also support NEOVM, and allow the writing of smart contracts with established languages, such as C# and Java. Elastos will be an OS for the Blockchain, and NEO can help developers quickly create Blockchain applications. The combination of the two could connect different developers from around the world, forming a strong ecosystem for application development―all to better serve a Smart Economy.
http://www.elastos.org/
https://twitter.com/ElastosI
https://www.reddit.com/NEO/comments/6r1a6f/neo_and_elastos_reaching_strategic_collaboration/
 
Ontology $ONT (Partnership with NEO)
Ontology Network (ONT) is a blockchain/distributed ledger network which combines distributed identity verification, data exchange, data collaboration, procedure protocols, communities, attestation, and various industry-specific modules. Together this builds the infrastructure for a peer-to-peer trust network which is cross-chain, cross-system, cross-industry, cross-application, and cross-device.
 
NEO will be the primary digital assets service provider for clearing and settlement on Ontology. There is no contract between Ontology and NEO now, though Ontology and NEO already have an established partnership. One thing on the roadmap is that in the future business scenarios on Ontology want to hold ICOs they will be able to on NEO.
https://ont.io/#/home
https://www.reddit.com/NEO/comments/7f8bvb/ontology_network_ama_answers/
https://www.youtube.com/watch?v=lPWwcgpc3P0
https://twitter.com/OntologyNetwork?lang=en
https://imgur.com/a/Emo4Q
 
The Key $TKY (Upcoming ICO ) (strategic cooperation with NEO)
THEKEY is a Decentralized Ecosystem of Identity Verification Tool Using National Big-data and Blockchain. THEKEY team is now developing second generation on-line identify verification technology. NEO Smart Economy = Digital Asset + Smart Contract + Digital Identity, while digital identity is an indispensable element. With NEO technical support, the strategic corporation between THEKEY and NEO will provide better protection to your digital asset.
https://www.thekey.vip/
https://www.reddit.com/NEO/comments/7areac/ama_on_9th_nov_thekey_a_decentralized_ecosystem/
 
Qlink $QLC (Partnership with NEO) (Multi-chain) (Upcoming ICO on NEO)
World’s First Decentralized Mobile Network
Qlink, a decentralized mobile network, is dedicated to constructing an open-source telecom infrastructure on blockchain.
https://twitter.com/QlinkMobi
https://www.qlink.mobi/f/qlink
https://neonewstoday.com/general/qlink-partner-with-neo/
 
PeerAtlas $ATLAS (Upcoming ICO on NEO)
ATLAS: A Digital Token Supporting an Open-Source Medical Encyclopedia
http://www.peeratlas.com/
http://www.peeratlas.com/whitepaper.pdf
https://neonewstoday.com/interviews/peeratlas-q-a-colin-closse
 
High Performance Blockchain $HPB (ICO Completed)
HPB is a new blockchain architecture, positioned as an easy-to-use, highperformance blockchain platform. It aims to extend the performance of distributed applications to meet real world business needs. This is achieved by creating an architecture similar to an API operating system. The software architecture provides accounts, identity and authorization management, policy management, databases, and asynchronous communication on thousands of CPUs, FPGAs or clustered program schedulers. This blockchain is a new architecture that can support millions of transactions per second and support authorizations within seconds.
http://www.gxn.io/en.html
http://www.gxn.io/files/hpb_white_paper_en.pdf
https://www.allcoin.com/markets/HPB-BTC/0/
 
Aphelion $APH (ICO In Progress)
A Revolutionary Decentralized P2P Exchange Solution
https://aphelion.org/
https://aphelion.org/wp.html
https://github.com/Aphelion
 
Zeepin $ZPT (Crowd sale will start Jan 18, 2018) (Upcoming ICO on NEO)
The Distributed Creative New Economy.
Zeepin, a decentralized innovation community, is dedicated to promoting highly efficient circulation of innovation assets.
https://www.zeepin.io/
https://www.zeepin.io/Whitepaper_En_v1.0.pdf
https://github.com/zeepin
https://www.reddit.com/NEO/comments/7f94vs/ama_from_today_nov_24th_zeepin_the_distributed/
 
Stokit (Upcoming ICO on NEO)
Decentralized cloud storage
https://stokit.io/
Whitepaper release: 30th of November 2017
 
Universal Health Coin (Upcoming ICO on NEO )
http://www.universalhealthcoin.com/
 
AdEx (dApp built on NEO)
http://adex.network/
https://twitter.com/AdEx_Network/status/897529249661423616
 
 
Alphacat
More Information to come soon after Video is released from the Meetup
https://www.meetup.com/de-DE/Onchains-Blockchain-Project-Launch-NEO-Ecosystem-Sharing/events/245101761/
 
DeepBrain
More Information to come soon after Video is released from the Meetup
https://www.meetup.com/de-DE/Onchains-Blockchain-Project-Launch-NEO-Ecosystem-Sharing/events/245101761/
 
 

City of Zion (CoZ)

https://cityofzion.io/
https://medium.com/@cityofzion
https://medium.com/proof-of-working
https://steemit.com/@canesin
 
City of Zion (CoZ) is an independent group of open source developers, designers and translators formed to support the NEO BlockChain core and ecosystem.
CoZ primarily operates through the community Slack and CoZ Github, central places where the community shares knowledge and contributes to projects.
CoZ is neither a corporation, nor a consulting firm or a devshop / for-hire group.
Members
https://imgur.com/a/Gc9jT
CoZ aims to be low barrier of entry, the process is straightforward:
  1. Join the channel #develop.
  2. Fork or create a project.
  3. Publish as open source.
  4. After a couple of contributions a CoZ council member will invite you to the proper channel for your contributions.
  5. Receive rewards and back to 3.
Unit testing - Ongoing effort to implement code coverage for the core
Integration testing - Tools for automated testing, performance metrics and functionality validation on private test nets
Continuous integration - Automated multi-platform testing of all pull requests at GitHub.
Deployment pipeline - Automated tools and processes to ensure fast and reliable updates upon code changes
New C# implementation (NEO2) - Improve code quality, speed & testability
 
Roadmap
https://imgur.com/a/4CDhw
 
dApps competition
https://cityofzion.io/dapps/1
10 prizes of 1350 GAS, with 500 GAS to be used for smart contract deployment.
Deadline was the 16 of November 11:59 EST.
http://cityofzion.io/dapps/1 (Check out page to view websites / Githubs)
1st: NEO Smart IoT
2nd: imusify
3rd: Chain Line
4th: BlockAuth
5th: Phantasma
6th: NeoTrade
7th: Turing Complete Smart Contract
8th: KRYPTON
9th: Switcheo
10th: TripShares
https://drive.google.com/drive/folders/0B4wu5lNlukwybEstaEJMZ19kbjQ
 

NEO and Microsoft China Dev Competition

 

Competition Rules

  1. The competition will open on November 20, 2017 and close at 11:59 PM Beijing time (GMT+8), March 10, 2018. Please sign up and submit your work before the deadline.
  2. Participants are required to develop on the NEO blockchain. Please refer to github.com/neo-project and docs.neo.org for relevant codes and technical documents.
  3. During the competition, developers are free to collaborate and to submit their work as a team.
  4. Teams or individuals who fail to submit their work before 11:59 PM Beijing time (GMT+8), March 10, 2018 will not be eligible for prizes.
  5. Your submission must contain executable programs and codes.
 
$150,000 First prize(1 team)
$50,000 Second prize(2 teams)
$30,000 Third prize(3 teams)
$15,000 Award of merit(10 teams)
 
A judging panel made up of NEO founder Da Hongfei,NEO Founder & Core Developer Erik Zhang, CoZ founder Fabio, Elastos founder Chen Rong,ONT Founder Li Jun and experts from Microsoft China will select 16 winners out of all the contestants for a bounty pool worth a total of USD 490,000.
 
Total sign-ups :194 Data collected as of 2017/11/28
 
Country sign-ups
China 48
USA 31
India 12
Norway 7
France 6
Other 90
 
https://neo.org/competition.html
 
 

ICO Firm

 
Projectico
A service that helps others launch a token sale if it is right for their cause and will be using NEO in most instances going forward. We have created a foundation that is bringing compliance and trust to the marketplace for ICOs and allowing international people to still participate.
https://www.projectico.io/
https://www.reddit.com/NEO/comments/7dd3s0/ama_on_20_nov_projectico_a_us_based_turnkey_token/
 
 

Key notes from the White Paper

http://docs.neo.org/en-us/
 
Digital Assets
Digital assets are programmable assets that exist in the form of electronic data. With blockchain technology, the digitization of assets can be decentralized, trustful, traceable, highly transparent, and free of intermediaries.
 
Digital Identity
Digital identity refers to the identity information of individuals, organizations, and other entities that exist in electronic form.
Our verification of identity when issuing or using digital identities includes the use of facial features, fingerprint, voice, SMS and other multi-factor authentication methods.
 
Smart Contracts
The NeoContract smart contract system is the biggest feature of the seamless integration of the existing developer ecosystem. Developers do not need to learn a new programming language but use C#, Java and other mainstream programming languages in their familiar IDE environments (Visual Studio, Eclipse, etc.) for smart contract development, debugging and compilation. NEO's Universal Lightweight Virtual Machine, NeoVM, has the advantages of high certainty, high concurrency, and high scalability. The NeoContract smart contract system will allow millions of developers around the world to quickly carry out the development of smart contracts.
 
Economic Model
NEO has two native tokens, NEOand NeoGas NEO represents the right to manage the network. Management rights include voting for bookkeeping, NEO network parameter changes, and so on. The minimum unit of NEO is 1 and tokens cannot be subdivided. GAS is the fuel token for the realization of NEO network resource control. The NEO network charges for the operation and storage of tokens and smart contracts, thereby creating economic incentives for bookkeepers and preventing the abuse of resources. The minimum unit of GAS is 0.00000001.
 
Distribution Mechanism
NEO's 100 million tokens are divided into two portions. The first portion is 50 million tokens distributed proportionally to supporters of NEO during the crowdfunding. This portion has been distributed.
The second portion is 50 million NEO managed by the NEO Council to support NEO's long-term development, operation and maintenance and ecosystem. The NEO in this portion has a lockout period of 1 year and is unlocked only after October 16, 2017. This portion will NOT enter the exchanges and is only for long-term support of NEO projects. The plans for it are as below:
▪ 10 million tokens (10% total) will be used to motivate NEO developers and members of the NEO Council
▪ 10 million tokens (10% total) will be used to motivate developers in the NEO ecosystem
▪ 15 million tokens (15% total) will be used to cross-invest in other block-chain projects, which are owned by the NEO Council and are used only for NEO projects
▪ 15 million (15% total) will be retained as contingency
▪ The annual use of NEO in principle shall NOT exceed 15 million tokens
 
GAS distribution
GAS is generated with each new block. The initial total amount of GAS is zero. With the increasing rate of new block generation, the total limit of 100 million GAS will be achieved in about 22 years. The interval between each block is about 15-20 seconds, and 2 million blocks are generated in about one year. According to this release curve, 16% of the GAS will be created in the first year, 52% of the GAS will be created in the first four years, and 80% of the GAS will be created in the first 12 years. GAS will be distributed proportionally in accordance with the NEO holding ratio, recorded in the corresponding addresses. NEO holders can initiate a claim transaction at any time and claim these GAS tokens at their holding addresses.
 
Consensus mechanism: dBFT
The dBFT is called the Delegated Byzantine Fault Tolerant, a Byzantine fault-tolerant consensus mechanism that enables large-scale participation in consensus through proxy voting. The holder of the NEO token can, by voting, pick the bookkeeper it supports. The selected group of bookkeepers, through BFT algorithm, reach a consensus and generate new blocks. Voting in the NEO network continues in real time, rather than in accordance with a fixed term.
 
Cross-chain assets exchange agreement
NeoX has been extended on existing double-stranded atomic assets exchange protocols to allow multiple participants to exchange assets across different chains and to ensure that all steps in the entire transaction process succeed or fail together. In order to achieve this function, we need to use NeoContract function to create a contract account for each participant. If other blockchains are not compatible with NeoContract, they can be compatible with NeoX as long as they can provide simple smart contract functionality.
 
Cross-chain distributed transaction protocol
Cross-chain distributed transactions mean that multiple steps of a transaction are scattered across different blockchains and that the consistency of the entire transaction is ensured. This is an extension of cross-chain assets exchange, extending the behavior of assets exchange into arbitrary behavior. In layman's terms, NeoX makes it possible for cross-chain smart contracts where a smart contract can perform different parts on multiple chains, either succeeding or reverting as a whole. This gives excellent possibilities for cross-chain collaborations and we are exploring cross-chain smart contract application scenarios.
 
Distributed Storage Protocol: NeoFS
NeoFS is a distributed storage protocol that utilizes Distributed Hash Table technology. NeoFS indexes the data through file content (Hash) rather than file path (URI). Large files will be divided into fixed-size data blocks that are distributed and stored in many different nodes
 
Anti-quantum cryptography mechanism: NeoQS
The emergence of quantum computers poses a major challenge to RSA and ECC-based cryptographic mechanisms. Quantum computers can solve the large number of decomposition problems (which RSA relies on) and the elliptic curve discrete logarithm (which ECC relies on) in a very short time. NeoQS (Quantum Safe) is a lattice-based cryptographic mechanism.
 

Reasons for choosing dBFT over PoW and PoS

 
With the phenomenal success of Bitcoin and its increasing mainstream adoption, the project’s unbounded appetite for energy grew accordingly. Today, the average Bitcoin transaction costs as much energy as powering 9.3 average American homes for 1 day.
https://digiconomist.net/bitcoin-energy-consumption#assumptions
This mind boggling amount of energy is not, as it is commonly believed, being wasted. It is put to good use: securing the Bitcoin network and rendering attacks on it infeasible. However, the cost of this security mechanism and its implications for an increasingly warming and resource hungry planet led almost the entire crypto industry to the understanding that an alternative has to be found, at least if we’re interested in seeing blockchain technology gaining overwhelming mainstream adoption.
The most popular alternative to PoW, used by most alternative cryptocurrency systems, is called Proof-of-Stake, or PoS. PoS is highly promising in the sense that it doesn’t require blockchain nodes to perform arduous, and otherwise useless, cryptographic tasks in order to render potential attacks costly and infeasible. Hence, this algorithm cuts the power requirements of PoS blockchains down to sane and manageable amounts, allowing them to be more scalable without guzzling up the planet's energy reserves.
As the name suggests, instead of requiring proof of cryptographic work, PoS requires blockchain nodes to proof stake in the currency itself. This means that in order for a blockchain node to be eligible for a verification reward, the node has to hold a certain amount of currency in the wallet associated with it. This way, in order to execute an attack, a malevolent node would have to acquire the majority of the existing coin supply, rendering attacks not only costly but also meaningless, since the attackers would primarily harm themselves.
PoS, as well as PoW, simply cause the blockchain to fork into two alternative versions if for some reason consensus breaks. In fact, most blockchains fork most of the time, only to converge back to a single source of truth a short while afterwards.
By many crypto enthusiasts, this obvious bug is very often regarded as a feature, allowing several versions of the truth to survive and compete for public adoption until a resolution is generated. This sounds nice in theory, but if we want to see blockchain technology seriously disrupt and/or augment the financial sector, this ever lurking possibility of the blockchain splitting into two alternative versions cannot be tolerated.
Furthermore, even the fastest PoS blockchains out there can accomodate a few hundred transactions per second, compare that to Visa’s 56,000 tx/s and the need for an alternative becomes clear as day.
A blockchain securing global stock markets does not have the privilege to fork into two alternative versions and just sit and wait it out until the market (or what’s left of it) declares a winner. What belongs to whom should be engraved in an immutable record, functioning as a single source of truth with no glitches permitted.
After investigating and studying the crypto industry and blockchain technologies for several years, we came to the conclusion that the delegated Byzantine Fault Tolerance alternative (or dBFT) is best suited for such a system. It provides swift transaction verification times, de-incentivises most attack vectors and upholds a single blockchain version with no risk of forks or alternative blockchain records emerging - regardless of how much computing power, or coins an attacker possesses.
The term Byzantine Fault Tolerance (BFT) derives its name from the Byzantine Generals problem in Game Theory and Computer Science, describing the problematic nature of achieving consensus in a distributed system with suboptimal communication between agents which do not necessarily trust each other.
The BFT algorithm arranges the relationship between blockchain nodes in such a way that the network becomes as good as resilient to the Byzantine Generals problem, and allows the system to remain consensus even if some nodes bare malicious intentions or simply malfunction.
To achieve this, Antshare’s version of the delegated BFT (or dBFT) algorithm acknowledges two kinds of players in the blockchain space: professional node operators, called bookkeeping nodes, who run nodes as a source of income, and users who are interested in accessing blockchain advantages. Theoretically, this differentiation does not exist in PoW and most PoS environments, practically, however, most Bitcoin users do not operate miners, which are mostly located in specialized venues run by professionals. At Antshares we understand the importance of this naturally occurring division of labor and use it to provide better security for our blockchain platform.
Accordingly, block verification is achieved through a consensus game held between specialized bookkeeping nodes, which are appointed by ordinary nodes through a form of delegated voting process. In every verification round one of the bookkeeping nodes is pseudo-randomly appointed to broadcast its version of the blockchain to the rest of the network. If ⅔ of the remaining nodes agree with this version, consensus is secured and the blockchain marches on. If less than ⅔ of the network agrees, a different node is appointed to broadcast its version of the truth to the rest of the system, and so forth until consensus is established.
In this way, successful system attacks are almost impossible to execute unless the overwhelming majority of the network is interested in committing financial suicide. Additionally, the system is fork proof, and at every given moment only one version of the truth exists. Without complicated cryptographic puzzles to solve, nodes operate much faster and are able to compete with centralized transaction methods.
https://www.econotimes.com/Blockchain-project-Antshares-explains-reasons-for-choosing-dBFT-over-PoW-and-PoS-659275
 

OnChain

 
It is important to note the technical difference between Onchain and NEO. Onchain is a private VC-backed company with over 40 employees. NEO is a public platform with different community-led groups contributing to this public project. There exists NEO council comprised of the original NEO creators, employees from Onchain, full time NEO council members and there is also the first Western based group called City of Zion.
Onchain, a Shanghai-based blockchain R&D company, first started developing Antshares in February of 2014 which will eventually become the foundation of DNA. Onchain was founded by CEO Da HongFei and CTO Erik Zhang in response to the attention from private companies garnered by the development of Antshares, China’s first public blockchain. In contrast to the weeks-old start-ups launching ICOs that is happening currently in the blockchain world, it took them 22 long months of R&D to even begin providing services to their first customers. Finally, in April 2016, the first whitepaper on consensus protocol from China was born — the dBFT (delegated Byzantine Fault Tolerance) protocol.
2016 was a busy year for Onchain and they really picked up the pace that year. Other than continuing the development of Antshares, brushing shoulders with Fortune 500 companies, Onchain became the first Chinese blockchain company to join Hyperledger — an open source blockchain project started by the Linux Foundation specifically focusing on the development of private and consortium chains for businesses.
In June of 2016, during the first of many future partnerships with Microsoft China, Onchain founded Legal Chain specifically targeting the inadequacies of the digital applications within the legal system. In 2005, (Digital Signature Act) was passed into national law which permitted an effective digital signatures to gain the same legal rights as a real signature.
In company with Microsoft China, they are also aiming to integrate the technology with Microsoft’s face and voice recognition API function to kick start this digital revolution within the legal system. At the same time, a partnership was formed with FaDaDa, a third-party platform for electronic contracts that has processed over 27 million contracts to date, to provide secure evidence storage with DNA. If that’s not enough, they were also voted as KPMG’s top 50 Fintech Company in China and established a relationship with the Japanese Ministry of Economy, Trade and Industry which led to the recent tour to Japan. Finally, at the end of 2016 they announced a partnership with Alibaba to provide attested email service for Ali Cloud with Legal Chain where it provides a proof-of-existence for a blockchain-powered email evidence repository for enterprise-level use.
Fosun Group, China’s largest private conglomerate, have recently invested into Onchain in order to apply DNA across all of its businesses. Currently, Fosun International has a market cap of 102.98 billion dollars on the Hong Kong Stock Exchange and that is only its international branch.
The role of Onchain so far is reminiscent of Ethereum’s EEA in addition to a stronger emphasis of governmental cooperation. Onchain has identified the shortcomings of present laser focus of hype on public platforms such as NEO and Ethereum and addressing that with DNA. DNA envisions a future where a network of assorted, specifically designed blockchains serving private enterprises, consortiums, government and the public communicating with each other forming an interconnected blockchain network.
This is the goal of DNA — infiltrating every little inefficient niche that had no better alternatives before the invention of blockchain. What is especially critical to remember during this explosive time of hype driven partly by the obscene degree of greed is that not every little niche that blockchain can fill will be holding its own little ICO. Some of those efficiencies gained will simply be consumed by companies privately or by public systems such as the legal system.
 
https://hackernoon.com/neo-onchain-and-its-ultimate-plan-dna-4c33e9b6bfaa
http://www.onchain.com/
https://github.com/DNAProject/DNA
https://siliconangle.com/blog/2016/10/20/onchain-partners-with-alibaba-for-blockchain-powered-email-evidence-repository/
https://www.reuters.com/article/us-fosun-blockchain/chinas-fosun-invests-in-local-version-of-bitcoin-tech-blockchain-idUSKCN1B30KM
 

Traveling

 
August 8th to August 12th
From August 8th to August 12th, 2017, the NEO core team, led by founder & CEO Da Hongfei will travel to Japan to explore the forefront of Japan's Blockchain innovation. This trip represents the first in a series of trips around the world with the goal to foster international cooperation's and to keep up with the fast pace in Blockchain innovation. Starting in Japan, the NEO core team will visit famous local Blockchain research institutions and active communities to engage in bilateral communication. NEO will meet with Japanese tech-celebrities to gain insights about the latest developments in the Japanese Blockchain and digital currency community. Additionally, Japanese local tech media will conduct an interview allowing NEO to present its development status and its latest technological innovations.
 
https://www.reddit.com/NEO/comments/6ry4s9/japan_the_neo_core_team_starts_out_on_an/
https://www.youtube.com/watch?v=SgTQ32CkxlU
https://www.reddit.com/NEO/comments/6ssfx1/neo_meetup_in_tokyo_august_10th_2017_2100h/
 
19th August, 2017
Blockchain X Series - NEO example applications
 
20th August, 2017
NEO and Microsoft Azure host a blockchain programming training in Shanghai
 
23rd August, 2017
INNOxNEO Blockchain Open Nights: 2nd Meeting
 
24th August, 2017
NEO Meetup in Taipei
 
13th September, 2017
INNOxNEO Blockchain Open Nights: 3rd Meeting
 
14th September, 2017
NEO Shanghai Meetup with NEO team
 
24th September, 2017
NEO Blockchain Programming Day - Hangzhou Station
 
27th September, 2017
INNOxNEO Blockchain Open Nights: 4th Meeting
 
27th September, 2017
First London NEO Developer Meetup!
 
4th October, 2017
First San Francisco NEO Developer Social!
 
14th-16th October, 2017
GNOME.Asia Summit 2017, Chongqing, China
 
21st October, 2017
NEO JOY, Exploring Blockchain application, Nanjing, China
 
26th October, 2017
Inaugural Global Fintech & Blockchain China Summit 2017
 
28th October, 2017
NEO meetup in Seoul, Korea:
 
28th October, 2017
NEO Blockchain Programming Day - Beijing Railway Station:
 
November 12th, 2017
NEO JOY in Hangzhou: Considerations on Basic Service Facilities in Blockchains:
 
November 18th - 19th, 2017
NEO attending China open source conference 2017:
 
November 21st, 2017
NEO attending swissnex China in Shanghai:
 
November 27th, 2017
ONCHAIN meetup NYC, Onchain's Blockchain Project Launch + NEO Ecosystem Sharing Session
 
November 27th, 2017
China&USA NEO blockchain meetup in Manhattan NYC
 
November 30th, 2017
Meetup San Francisco: The Future Of Blockchain With The Founders of NEO, Elastos, & Stellar
 
December 4th, 2017
NEO attending Blockchain World Conference in Bangkok:
 
December 7th, 2017
NEO meetup Singapore:
 
December 13th, 2017
NEO meetup at Cambridge:
 

Networks proves itself with the first ICO

 
ICOs, on other platforms such as Ethereum, often resulted in a sluggish network and transaction delays. While NEO’s dBFT consensus algorithm is designed to achieve consensus with higher efficency and greater network throughputt, no amount of theoretical calculations can simulate the reality of real-life conditions.
 

Key Observations

 
Smart Contract Invocations:
A total of 13,966 smart contracts invocations were executed on the NEO network over this time period, of which, nearly all called the RPX smart contract method mintTokens. A total of 543,348,500 RPX tokens were successfully minted and transferred to user accounts, totalling 10,097 smart contract executions.
 
Refunded Invocations:
A total of 4182 refund events were triggered by the smart contract method mintTokens. (Note: RPX has stated that these refunds will be processed within the next two weeks.)
 
Crowdsale Statistics:
A successful mintTokens execution used around 1043 VM operations, while an execution that resulted in a refund used 809 VM operations. Within the hour and six minutes that the token sale was active, a total of 12,296,409 VM operations were executed. A total of 9,575 unique addresses participated in the RPX ICO. Half of these, approximately 4,800 unique addresses, participated through CoZ’s Neon wallet. The top 3 blocks with the most transactions were block 1445025 (3,242 transactions), block 1444902 (2,951 transactions), and block 1444903 (1609 transactions).
 
Conclusion on Network Performance
At the moment, the consensus nodes for the NEO network are operated by the NEO Council in China. By Q1 2018, NEO Council aims to control less than two-thirds of the consensus nodes.
We are pleased to note that the NEO network continuted to operate efficiently with minimal network impact, even under extreme network events. Block generation time initially slowed down to 3 minutes to process the largest block, but quickly recovered to approximately 25 seconds. Throughout the entire RPX ICO, consensus nodes were able to achieve consensus and propagate new block transactions to the rest of the network. In closing, while we consider this performance to be excellent, NEO Council and City of Zion areworking closely together on upgrades, that will increase the throughputs of the NEO network.
 

Hyperledger

 
Members and governance of Hyperledger:
Early members of the initiative included blockchain ISVs, (Blockchain, ConsenSys, Digital Asset, R3, Onchain), well-known technology platform companies (Cisco, Fujitsu, Hitachi, IBM, Intel, NEC, NTT DATA, Red Hat, VMware), financial services firms (ABN AMRO, ANZ Bank, BNY Mellon, CLS Group, CME Group, the Depository Trust & Clearing Corporation (DTCC), Deutsche Börse Group, J.P. Morgan, State Street, SWIFT, Wells Fargo), Business Software companies like SAP, Systems integrators and others such as: (Accenture, Calastone, Credits, Guardtime, IntellectEU, Nxt Foundation, Symbiont).
The governing board of the Hyperledger Project consists of twenty members chaired by Blythe Masters, (CEO of Digital Asset), and a twelve-member Technical Steering Committee chaired by Christopher Ferris, CTO of Open Technology at IBM.
http://www.8btc.com/onchain-hyperledger
https://en.wikipedia.org/wiki/Hyperledger
 
“As a leading open-source contributor in China’s blockchain community, Onchain shares the same values as the Linux Foundation and the Hyperledger project intrinsically. We believe international collaboration plus local experience are key to the adoption of distributed ledger technology in China; we are also very excited to see other Chinese blockchain startups join Hyperledger and look forward to adding our combined expertise to the project.” Da Hongfei, Founder and CEO of Onchain
https://hyperledger.org/testimonials/onchain
 

Important Articles

 
Response to baseless FUD
https://medium.com/@MalcolmLerideresponse-to-baseless-fud-9b7e5e2eeeea
 
Distribution technology DNA framework went through the national block chain standard test On May 16th, the first China block chain development competition in Hangzhou announced that Onchain, became the first through the national standard test block system.
http://www.51cto.com/art/201705/539824.htm?mobile
 
Da Hongfei and OnChain working relationship with Chinese Government
https://finance.sina.cn/2017-04-13/detail-ifyeifqx5554606.d.html?from=wap
http://www.gz.chinanews.com/content/2017/05-28/73545.shtml
 
The Chinese government is reportedly preparing to allow the resumption of cryptocurrency trading in the country in the coming months, with the required anti-money laundering (AML) systems and licensing programs in place.
https://coingeek.com/cryptocurrency-trading-poised-to-make-a-return-in-china-report/
 
Japanese Ministry of Economy, Trade and Industry - Working with OnChain and NEO
http://www.8btc.com/onchain-ribenjingjichanyesheng
 
Notice NEO will be invited to attend the INNO x Austrade China-Australia chain high-end exchange
AUSTRADE - The Australian Trade and Investment Commission is the official government, education and investment promotion agency of the Australian Government
https://mp.weixin.qq.com/s/LmXnW7MtzOX_fqIo7diU9A
 
Source for NEO/OnChain Microsoft Cooperation:
http://www.8btc.com/onchain-microsoft
 

Da Hongfei quotes

 
"There is no direct cooperation between Alibaba and NEO/Onchain, other than their mailbox service is using Law Chain to provide attested email service. In terms of Microsoft, yes we have cooperation with Microsoft China because NEO is built with C# and .NET Core, and NeoContract is the first in the world to support writing smart contract with C#"
https://www.reddit.com/NEO/comments/6puffo/we_are_da_hongfei_and_erik_zhang_founders_of_neo/dksm5ga/
 
"We have pretty good communication with government, with regulators. They don't have any negative impression with NEO and they like our technology and the way we deal with things. Regulation is not an issue for us"
https://www.youtube.com/watch?v=qpUdTIQdjVE&feature=youtu.be&t=1m16s
 
“Before they started cleaning up the market, I was asked for information and suggestions” “I do not expect the government to call me in the short-term and say, ‘Let’s use NEO as the blockchain technology infrastructure of China.’ But in the medium term? Why not? I think it’s possible.”
https://medium.com/@TheCoinEconomy/neo-founder-da-hongfei-advised-china-on-ico-exchange-ban-says-govt-4631b9f7971
 

Upcoming Roadmap

 
Decentralization of consensus nodes
▪ P2P Network optimization – Network optimizations to ensure fast block generation after decentralization.
▪ Voting Algorithm Optimization – Adjustments in voting algorithm to prevent identified attack vectors.
▪ Candidate List Website – Published list of candidates so that voters know who they are voting for.
▪ NEO Council Consensus Node < 2/3 – NEO Council shall operate less than two thirds of consensus nodes by the end of quarter 1, 2018.
 
Our original plan was to start decentralize in Q1 2018. We are however growing faster than expected and cannot accept the risk with being as centralized as we currently are. The conclusion is that we re-prioritize and start the process of decentralizing today. We believe that NEO community groups and exchanges will be suitable to run consensus nodes; community groups already know the technology, and exchanges are already running full nodes with high uptime and monitoring. We welcome interested parties to reach out to us on [email protected]. A NEP to encourage voting will be presented in the coming weeks.
https://neo.org/blog/Details/3016
 
Universal Data Format for Wallet/Node Prog.
▪ NEP2 – Private Key Encryption/Decryption (2017Q4) - Method for encrypting and encoding a passphrase-protected private key.
▪ NEP3 – Universal Data Format (2017Q4) – Standard data format to allow easier wallet and node programming.
https://neo.org/en-us/blog/details/65
 
Promotion/Ecosystem
▪ Globally Legal Token-raising Framework (2017Q4) – Following government interest to regulate ICO’s, NEO will complete a framework to raise tokens legally in all major markets by the end of 2017.
▪ NEO DevCon 1 (2017Q4) – First NEO Development Conference! More details at later date.
▪ CoZ Funding (2017Q4) – Continuous funding plan for CoZ covering next 5 years.
▪ Seed Projects (2017Q4) – First seed projects to be cross-invested with the dedicated NEO pool.
https://neo.org/en-us/blog/details/65
 

NEO Github

https://github.com/neo-project
 
NEO Smart Economy https://github.com/neo-project/neo
1.2k Stars
383 Forks
327 commits
17 contributors
 
neo-gui https://github.com/neo-project/neo-gui
 
examples-csharp https://github.com/neo-project/examples-csharp
 
proposals https://github.com/neo-project/proposals
 
 

CityOfZion Github

https://github.com/CityOfZion
 
awesome-neo https://github.com/CityOfZion/awesome-neo
A curated list of awesome NEO libraries, applications and resources.
14 contributors
 
neon-wallet https://github.com/CityOfZion/neon-wallet
380 Stars
118 Forks
392 commits
29 contributors
 

DNAProject Github

https://github.com/DNAProject/DNA
 
NEO/GAS Donations welcome: ASdNxSa3E8bsxCE9KFKBMm3NA43sYJU9qZ
submitted by NEOcryptotrader to NEO [link] [comments]

1mb Fork Txn

Enclosed find a signed 1mb txn (999,957 bytes), that if mined will fork the network. TxnID: bbb67fc3320d1e9a58c7cd0bb5ead2cff87b243e089e4a21dad669ba28703f32
The outputs of this transaction have the following function, designated by their prefix:
The 1mb signed txn: https://anonfile.com/N2T4Aeb0bb/1mbtxn.txt
Once a client is available that will support relay of this txn, the console interface will likely not support it. To push this txn you'll have to use the RPC interface with a script https://en.bitcoin.it/wiki/API_reference_(JSON-RPC)
from bitcoinrpc.authproxy import AuthServiceProxy, JSONRPCException
rpc_user="Your_User"
rpc_password="Your_Pass"
rpc_connection = AuthServiceProxy("http://%s:%[email protected]:8332"%(rpc_user, rpc_password))
txn = []
f = open('1mbtxn.txt', 'r') #This is the above linked txt file containing the txn
txn = f.read()
f.close()
print(rpc_connection.sendrawtransaction(txn))
if you get this error, your client does not support this txn
64: tx-size
submitted by 1MBforKTR1gAqRLkNbQg to btc [link] [comments]

Email received: This account is now infected!

Email only (work address) no evidence of password breach .. Other than reporting to bitcoinwhoswho.com and otherwise ignoring is there anything to be done? I realize that a sender address can be spoofed so is it possible that the from address ([email protected]) in the header below is not the real sender? Seems to be a Brazilian molded concrete company.
Email text, header below: This account is now infected! Change the pswd right this moment! You might not know me me and you obviously are definitely wanting to know why you are getting this particular electronic message, proper? I'm ahacker who crackedyour emailand digital devicesa few months ago. Do not try out to communicate with me or seek for me, it's hopeless, since I directed you this message from YOUR hacked account. I have installed special program on the adult videos (porn) site and guess you visited this website to have a good time (you understand what I mean). During you have been watching vids, your internet browser started out to act like a RDP (Remote Control) with a keylogger that granted me authority to access your monitor and camera. Then, my applicationgatheredall info. You have typed passcodes on the web services you visited, I intercepted them. Without a doubt, you are able change them, or already modified them. Even so it doesn't matter, my program renews needed data every 5 minutes. What did I do? I got a reserve copy of your system. Of all files and contacts. I created a dual-screen video recording. The 1 part shows the film you were watching (you have the perfect taste, huh...), and the 2nd screen presents the tape from your own web camera. What actually do you have to do? Good, I believe, 1000 USD is a good price for our little riddle. You will make the deposit by bitcoins (if you do not know this, search “how to purchase bitcoin” in Google). My bitcoin wallet address: 1LAWGnA2K5njVSshERU9bcUSrW2YWwtXs1 (It is cAsE sensitive, so copy and paste it). Attention: You have 2 days in order to make the payment. (I built in an exclusive pixel in this letter, and from now I know that you've read through this email). To tracethe reading of a letterand the actionswithin it, I installeda Facebook pixel. Thanks to them. (Anything thatis usedfor the authorities should helpus.)
In case I fail to get bitcoins, I'll immediately direct your video to each of your contacts, including relatives, co-workers, and many more?
Header:
Return-Path: [email protected] Delivered-To: [email protected] Received: from cloud126.hostgator.com by cloud126.hostgator.com with LMTP id yOIWL8YsbFz2cQoAEuG05A for [email protected]; Tue, 19 Feb 2019 10:20:22 -0600 Return-path: [email protected] Envelope-to: [email protected] Delivery-date: Tue, 19 Feb 2019 10:20:22 -0600 Received: from hm1481-n-158.locaweb.com.br ([189.126.112.158]:21734) by cloud126.hostgator.com with esmtp (Exim 4.91) (envelope-from [email protected]) id 1gw885-002sin-RV for [email protected]; Tue, 19 Feb 2019 10:20:22 -0600 Received: from mcbain0015.correio.biz (201.76.49.38) by hm1481.locaweb.com.br id hdgmc4169v03 for [email protected]; Tue, 19 Feb 2019 13:20:03 -0300 (envelope-from [email protected]) Received: from proxy.email-ssl.com.br (bartf0018.email.locaweb.com.br [10.31.120.50]) by mcbain0015.correio.biz (Postfix) with ESMTP id D4969400300 for [email protected]; Tue, 19 Feb 2019 13:20:04 -0300 (-03) x-locaweb-id: qZRjVrKfkakdSxdDkiArSqul_N16C3UN17lli1H_acU9zZR1_VnvSsTpjbeqGI6c2HJsKkJhRLItjjqbrEcJ4S-lcgqvnzQJbDSRWCSjkNsOJt8ejVwgqWPVqsHwgvFQPBD0MKt5gdHXA59jz_7OFn7gakRaOm2owEMQqwf69LiyetPRte3nY2CkTrNrXW1gQdtnl1cDYoJjSbpwi5AmudTaoyBuD3bKM29bCzv1BqY= NjY3MjYxNmU2MzY5NzM2MzZmNDA3NjY5NjI3MjZmNzQ2ZjZlMmU2MzZmNmQyZTYyNzI= X-LocaWeb-COR: locaweb_2009_x-mail X-AuthUser: [email protected] Received: from [168.90.183.91.ssinet.com.br] (168.90.183.170.ssinet.com.br [168.90.183.170]) (Authenticated sender: [email protected]) by proxy.email-ssl.com.br (Postfix) with ESMTPSA id BDC961840703 for [email protected]; Tue, 19 Feb 2019 13:20:03 -0300 (-03) To: [email protected] X-Priority: 5 (Lowest) List-Unsubscribe: https://vibroton.com.bunsubscribe/e/14213/1if2dfy6e5jj3wtuublu1a8dytvi05dzw35n8uuajyxc1ibrc7xep5jm9j62mloc/086346591 Content-Transfer-Encoding: base64 Content-Type: text/plain; charset=UTF-8 Date: Tue, 19 Feb 2019 17:20:04 +0100 Subject: X-aid: 2720599631 X-Mailer: Zimbra 7.2.4_GA_2903 (ZimbraWebClient - FF3.0 (Win)/7.2.4_GA_2900) Message-ID: [email protected] Abuse-Reports-To: [email protected] From: [email protected] X-Spam-Status: No, score=0.5 X-Spam-Score: 5 X-Spam-Bar: / X-Spam-Flag: NO
submitted by rmccl54 to hacker [link] [comments]

Another victim of ibittreix.com

Hello, like a preveois poster who lost 6 btc to this scam i too have been cleared out of my complete account, and all my savings 3.49118btc. Absolutely heartbreaking as can see the trail going from my acc after ibittreix conned me, then through another wallet and now sitting on a blockchain wallet with a nice round 250btc total. Kicks in the gut knowing i messed up, top search result with google was the phishing site and apparently it was up for 3 days previous to me being duped. Just stopped my proxy server torguard, went onto tge phishing site and it asked for details, as as ip change was noted. Because i had stopped my proxy and had been on bittrex an hour earlier i only clicked i was being duped after signing in, then getting very real looking google mail security page to get a code sent to my phone. By this the hackers had my gmail details, phone and bittrex details. So gutted i didnt twig. I reported it after trying to get into my account for 30 mins, 5 day till cut and paste faq reply from bittrex. Then 2 more days till they reset google auth. Asked day 1 to confirm my funds were safe. So low right now its unreal. I know its lost forever, and 3.5btc was alot to me. I invested it that week at binance. Only transferred to bittrex on the day it was stolen and never had a single trade. Hacker changed my usdt which i transferred all to btc... Then withdrew them to their wallet. Naive yes but absolutely gutted. Lost 9.5 thousand pounds that i had decided to invest in bitcoin. Now nothing left. Bad week for me. Future is bleak. Tough lesson to learn from. Stay safe people, its not a fair world.
submitted by Paulforthers to Bitcoin [link] [comments]

Exchanged.i2p Anonymous Exchange

EXCHANGED.I2P
Anonymous Crypto Currency Exchange July 9 2015
GRAND OPENING! We at exchanged.i2p are happy to announce the grand opening of exchanged.i2p(beta) the worlds first fully anonymous crypto currency exchange. We hope you enjoy it as much as we enjoyed developing it. The site can be access directly via I2P, simply download I2P from https://geti2p.org/ and set your browser to use the http proxy at localhost port 4444. You may also access the site via an I2P inproxy such as https://i2p.us/ with limited functionality over tor or the clearnet. If you have trouble accessing the exchange via exchanged.i2p please try: http://ylmulgfskl6uiwac4hw4ecwqdzd3oxtwaemzj25zc6k5q4rkexra.b32.i2p
FREE COINS on IRC: We are constantly raining free coins from multiple tip bots in our IRC2P channel.
Start I2P Point your irc client at 127.0.0.1:6668 /join #exchange
Key Features: Standard buy/sell orders Bote support Password only login PGP only(no username) login Dual auth(Password&PGP) login Darkpool trades off orderbook Instant trades filled at any price
Supported Currencies: Anoncoin ANC Bitcoin BTC Dogecoin DOGE Dogecoindark DOGED Litecoin LTC Peercoin PPC Primecoin XMP Vertcoin VTC
Coming Soon: Bitshares BTS Blackcoin BLK Dash DASH Monero XMR Namecoin NMC Nubits NBT Ybcoin YBC
Features in Development: More coins Trading API Margin trades Short trades Stop orders More charts Desktop trading client
Contact:
[email protected] GPG: ExchangeD.i2p/contact https://bitcointalk.org/index.php?topic=1092682.0
Please report any bugs or problems immediately.
submitted by kitsu_exchange to CryptoCurrency [link] [comments]

The most interesting nmap result I've seen after scanning tens of thousands of addresses around my local net [dissect/discuss]

Nmap scan report for [neighborhood].2.243 Host is up (0.096s latency). PORT STATE SERVICE 1/tcp open tcpmux 3/tcp open compressnet 4/tcp open unknown 6/tcp open unknown 7/tcp open echo 9/tcp open discard 13/tcp open daytime 17/tcp open qotd 19/tcp open chargen 20/tcp open ftp-data 21/tcp open ftp 22/tcp open ssh 23/tcp open telnet 24/tcp open priv-mail 25/tcp filtered smtp 26/tcp open rsftp 30/tcp open unknown 32/tcp open unknown 33/tcp open dsp 37/tcp open time 42/tcp open nameserver 43/tcp open whois 49/tcp open tacacs 53/tcp open domain 70/tcp open gopher 79/tcp open finger 80/tcp open http 81/tcp open hosts2-ns 82/tcp open xfer 83/tcp open mit-ml-dev 84/tcp open ctf 85/tcp open mit-ml-dev 88/tcp open kerberos-sec 89/tcp open su-mit-tg 90/tcp open dnsix 99/tcp open metagram 100/tcp open newacct 106/tcp open pop3pw 109/tcp open pop2 110/tcp open pop3 111/tcp open rpcbind 113/tcp filtered ident 119/tcp open nntp 125/tcp open locus-map 135/tcp filtered msrpc 139/tcp open netbios-ssn 143/tcp open imap 144/tcp open news 146/tcp open iso-tp0 161/tcp open snmp 163/tcp open cmip-man 179/tcp open bgp 199/tcp open smux 211/tcp open 914c-g 212/tcp open anet 222/tcp open rsh-spx 254/tcp open unknown 255/tcp open unknown 256/tcp open fw1-secureremote 259/tcp open esro-gen 264/tcp open bgmp 280/tcp open http-mgmt 301/tcp open unknown 306/tcp open unknown 311/tcp open asip-webadmin 340/tcp open unknown 366/tcp open odmr 389/tcp open ldap 406/tcp open imsp 407/tcp open timbuktu 416/tcp open silverplatter 417/tcp open onmux 425/tcp open icad-el 427/tcp open svrloc 443/tcp open https 444/tcp open snpp 445/tcp open microsoft-ds 458/tcp open appleqtc 464/tcp open kpasswd5 465/tcp open smtps 481/tcp open dvs 497/tcp open retrospect 500/tcp open isakmp 512/tcp open exec 513/tcp open login 514/tcp open shell 515/tcp open printer 524/tcp open ncp 541/tcp open uucp-rlogin 543/tcp open klogin 544/tcp open kshell 545/tcp open ekshell 548/tcp open afp 554/tcp open rtsp 555/tcp open dsf 563/tcp open snews 587/tcp open submission 593/tcp open http-rpc-epmap 616/tcp open sco-sysmgr 617/tcp open sco-dtmgr 625/tcp open apple-xsrvr-admin 631/tcp open ipp 636/tcp open ldapssl 646/tcp open ldp 648/tcp open rrp 666/tcp open doom 667/tcp open disclose 668/tcp open mecomm 683/tcp open corba-iiop 687/tcp open asipregistry 691/tcp open resvc 700/tcp open epp 705/tcp open agentx 711/tcp open cisco-tdp 714/tcp open iris-xpcs 720/tcp open unknown 722/tcp open unknown 726/tcp open unknown 749/tcp open kerberos-adm 765/tcp open webster 777/tcp open multiling-http 783/tcp open spamassassin 787/tcp open qsc 800/tcp open mdbs_daemon 801/tcp open device 808/tcp open ccproxy-http 843/tcp open unknown 873/tcp open rsync 880/tcp open unknown 888/tcp open accessbuilder 898/tcp open sun-manageconsole 900/tcp open omginitialrefs 901/tcp open samba-swat 902/tcp open iss-realsecure 903/tcp open iss-console-mgr 911/tcp open xact-backup 912/tcp open apex-mesh 981/tcp open unknown 987/tcp open unknown 990/tcp open ftps 992/tcp open telnets 993/tcp open imaps 995/tcp open pop3s 999/tcp open garcon 1000/tcp open cadlock 1001/tcp open unknown 1002/tcp open windows-icfw 1007/tcp open unknown 1009/tcp open unknown 1010/tcp open surf 1011/tcp open unknown 1021/tcp open exp1 1022/tcp open exp2 1023/tcp open netvenuechat 1024/tcp open kdm 1025/tcp open NFS-or-IIS 1026/tcp open LSA-or-nterm 1027/tcp open IIS 1028/tcp open unknown 1029/tcp open ms-lsa 1030/tcp open iad1 1031/tcp open iad2 1032/tcp open iad3 1033/tcp open netinfo 1034/tcp open zincite-a 1035/tcp open multidropper 1036/tcp open nsstp 1037/tcp open ams 1038/tcp open mtqp 1039/tcp open sbl 1040/tcp open netsaint 1041/tcp open danf-ak2 1042/tcp open afrog 1043/tcp open boinc 1044/tcp open dcutility 1045/tcp open fpitp 1046/tcp open wfremotertm 1047/tcp open neod1 1048/tcp open neod2 1049/tcp open td-postman 1050/tcp open java-or-OTGfileshare 1051/tcp open optima-vnet 1052/tcp open ddt 1053/tcp open remote-as 1054/tcp open brvread 1055/tcp open ansyslmd 1056/tcp open vfo 1057/tcp open startron 1058/tcp open nim 1059/tcp open nimreg 1060/tcp open polestar 1061/tcp open kiosk 1062/tcp open veracity 1063/tcp open kyoceranetdev 1064/tcp open jstel 1065/tcp open syscomlan 1066/tcp open fpo-fns 1067/tcp open instl_boots 1068/tcp open instl_bootc 1069/tcp open cognex-insight 1070/tcp open gmrupdateserv 1071/tcp open bsquare-voip 1072/tcp open cardax 1073/tcp open bridgecontrol 1074/tcp open warmspotMgmt 1075/tcp open rdrmshc 1076/tcp open sns_credit 1077/tcp open imgames 1078/tcp open avocent-proxy 1079/tcp open asprovatalk 1080/tcp open socks 1081/tcp open pvuniwien 1082/tcp open amt-esd-prot 1083/tcp open ansoft-lm-1 1084/tcp open ansoft-lm-2 1085/tcp open webobjects 1086/tcp open cplscrambler-lg 1087/tcp open cplscrambler-in 1088/tcp open cplscrambler-al 1089/tcp open ff-annunc 1090/tcp open ff-fms 1091/tcp open ff-sm 1092/tcp open obrpd 1093/tcp open proofd 1094/tcp open rootd 1095/tcp open nicelink 1096/tcp open cnrprotocol 1097/tcp open sunclustermgr 1098/tcp open rmiactivation 1099/tcp open rmiregistry 1100/tcp open mctp 1102/tcp open adobeserver-1 1104/tcp open xrl 1105/tcp open ftranhc 1106/tcp open isoipsigport-1 1107/tcp open isoipsigport-2 1108/tcp open ratio-adp 1110/tcp open nfsd-status 1111/tcp open lmsocialserver 1112/tcp open msql 1113/tcp open ltp-deepspace 1114/tcp open mini-sql 1117/tcp open ardus-mtrns 1119/tcp open bnetgame 1121/tcp open rmpp 1122/tcp open availant-mgr 1123/tcp open murray 1124/tcp open hpvmmcontrol 1126/tcp open hpvmmdata 1130/tcp open casp 1131/tcp open caspssl 1132/tcp open kvm-via-ip 1137/tcp open trim 1138/tcp open encrypted_admin 1141/tcp open mxomss 1145/tcp open x9-icue 1147/tcp open capioverlan 1148/tcp open elfiq-repl 1149/tcp open bvtsonar 1151/tcp open unizensus 1152/tcp open winpoplanmess 1154/tcp open resacommunity 1163/tcp open sddp 1164/tcp open qsm-proxy 1165/tcp open qsm-gui 1166/tcp open qsm-remote 1169/tcp open tripwire 1174/tcp open fnet-remote-ui 1175/tcp open dossier 1183/tcp open llsurfup-http 1185/tcp open catchpole 1186/tcp open mysql-cluster 1187/tcp open alias 1192/tcp open caids-sensor 1198/tcp open cajo-discovery 1199/tcp open dmidi 1201/tcp open nucleus-sand 1213/tcp open mpc-lifenet 1216/tcp open etebac5 1217/tcp open hpss-ndapi 1218/tcp open aeroflight-ads 1233/tcp open univ-appserver 1234/tcp open hotline 1236/tcp open bvcontrol 1244/tcp open isbconference1 1247/tcp open visionpyramid 1248/tcp open hermes 1259/tcp open opennl-voice 1271/tcp open excw 1272/tcp open cspmlockmgr 1277/tcp open miva-mqs 1287/tcp open routematch 1296/tcp open dproxy 1300/tcp open h323hostcallsc 1301/tcp open ci3-software-1 1309/tcp open jtag-server 1310/tcp open husky 1311/tcp open rxmon 1322/tcp open novation 1328/tcp open ewall 1334/tcp open writesrv 1352/tcp open lotusnotes 1417/tcp open timbuktu-srv1 1433/tcp open ms-sql-s 1434/tcp open ms-sql-m 1443/tcp open ies-lm 1455/tcp open esl-lm 1461/tcp open ibm_wrless_lan 1494/tcp open citrix-ica 1500/tcp open vlsi-lm 1501/tcp open sas-3 1503/tcp open imtc-mcs 1521/tcp open oracle 1524/tcp open ingreslock 1533/tcp open virtual-places 1556/tcp open veritas_pbx 1580/tcp open tn-tl-r1 1583/tcp open simbaexpress 1594/tcp open sixtrak 1600/tcp open issd 1641/tcp open invision 1658/tcp open sixnetudr 1666/tcp open netview-aix-6 1687/tcp open nsjtp-ctrl 1688/tcp open nsjtp-data 1700/tcp open mps-raft 1717/tcp open fj-hdnet 1718/tcp open h323gatedisc 1719/tcp open h323gatestat 1720/tcp open h323q931 1721/tcp open caicci 1723/tcp open pptp 1755/tcp open wms 1761/tcp open landesk-rc 1782/tcp open hp-hcip 1783/tcp open unknown 1801/tcp open msmq 1805/tcp open enl-name 1812/tcp open radius 1839/tcp open netopia-vo1 1840/tcp open netopia-vo2 1862/tcp open mysql-cm-agent 1863/tcp open msnp 1864/tcp open paradym-31 1875/tcp open westell-stats 1900/tcp open upnp 1914/tcp open elm-momentum 1935/tcp open rtmp 1947/tcp open sentinelsrm 1971/tcp open netop-school 1972/tcp open intersys-cache 1974/tcp open drp 1984/tcp open bigbrother 1998/tcp open x25-svc-port 1999/tcp open tcp-id-port 2000/tcp open cisco-sccp 2001/tcp open dc 2002/tcp open globe 2003/tcp open finger 2004/tcp open mailbox 2005/tcp open deslogin 2006/tcp open invokator 2007/tcp open dectalk 2008/tcp open conf 2009/tcp open news 2010/tcp open search 2013/tcp open raid-am 2020/tcp open xinupageserver 2021/tcp open servexec 2022/tcp open down 2030/tcp open device2 2033/tcp open glogger 2034/tcp open scoremgr 2035/tcp open imsldoc 2038/tcp open objectmanager 2040/tcp open lam 2041/tcp open interbase 2042/tcp open isis 2043/tcp open isis-bcast 2045/tcp open cdfunc 2046/tcp open sdfunc 2047/tcp open dls 2048/tcp open dls-monitor 2049/tcp open nfs 2065/tcp open dlsrpn 2068/tcp open avocentkvm 2099/tcp open h2250-annex-g 2100/tcp open amiganetfs 2103/tcp open zephyr-clt 2105/tcp open eklogin 2106/tcp open ekshell 2107/tcp open msmq-mgmt 2111/tcp open kx 2119/tcp open gsigatekeeper 2121/tcp open ccproxy-ftp 2126/tcp open pktcable-cops 2135/tcp open gris 2144/tcp open lv-ffx 2160/tcp open apc-2160 2161/tcp open apc-agent 2170/tcp open eyetv 2179/tcp open vmrdp 2190/tcp open tivoconnect 2191/tcp open tvbus 2196/tcp open unknown 2200/tcp open ici 2222/tcp open EtherNetIP-1 2251/tcp open dif-port 2260/tcp open apc-2260 2288/tcp open netml 2301/tcp open compaqdiag 2323/tcp open 3d-nfsd 2366/tcp open qip-login 2381/tcp open compaq-https 2382/tcp open ms-olap3 2383/tcp open ms-olap4 2393/tcp open ms-olap1 2394/tcp open ms-olap2 2399/tcp open fmpro-fdal 2401/tcp open cvspserver 2492/tcp open groove 2500/tcp open rtsserv 2522/tcp open windb 2525/tcp open ms-v-worlds 2557/tcp open nicetec-mgmt 2601/tcp open zebra 2602/tcp open ripd 2604/tcp open ospfd 2605/tcp open bgpd 2607/tcp open connection 2608/tcp open wag-service 2638/tcp open sybase 2701/tcp open sms-rcinfo 2702/tcp open sms-xfer 2710/tcp open sso-service 2717/tcp open pn-requester 2718/tcp open pn-requester2 2725/tcp open msolap-ptp2 2800/tcp open acc-raid 2809/tcp open corbaloc 2811/tcp open gsiftp 2869/tcp open icslap 2875/tcp open dxmessagebase2 2909/tcp open funk-dialout 2910/tcp open tdaccess 2920/tcp open roboeda 2967/tcp open symantec-av 2968/tcp open enpp 2998/tcp open iss-realsec 3000/tcp closed ppp 3001/tcp open nessus 3003/tcp open cgms 3005/tcp open deslogin 3006/tcp open deslogind 3007/tcp open lotusmtap 3011/tcp open trusted-web 3013/tcp open gilatskysurfer 3017/tcp open event_listener 3030/tcp open arepa-cas 3031/tcp open eppc 3052/tcp open powerchute 3071/tcp open csd-mgmt-port 3077/tcp open orbix-loc-ssl 3128/tcp open squid-http 3168/tcp open poweronnud 3211/tcp open avsecuremgmt 3221/tcp open xnm-clear-text 3260/tcp open iscsi 3261/tcp open winshadow 3268/tcp open globalcatLDAP 3269/tcp open globalcatLDAPssl 3283/tcp open netassistant 3300/tcp open unknown 3301/tcp open unknown 3306/tcp open mysql 3322/tcp open active-net 3323/tcp open active-net 3324/tcp open active-net 3325/tcp open active-net 3333/tcp open dec-notes 3351/tcp open btrieve 3367/tcp open satvid-datalnk 3369/tcp open satvid-datalnk 3370/tcp open satvid-datalnk 3371/tcp open satvid-datalnk 3372/tcp open msdtc 3389/tcp open ms-wbt-server 3390/tcp open dsc 3404/tcp open unknown 3476/tcp open nppmp 3493/tcp open nut 3517/tcp open 802-11-iapp 3527/tcp open beserver-msg-q 3546/tcp open unknown 3551/tcp open apcupsd 3580/tcp open nati-svrloc 3659/tcp open apple-sasl 3689/tcp open rendezvous 3690/tcp open svn 3703/tcp open adobeserver-3 3737/tcp open xpanel 3766/tcp open unknown 3784/tcp open bfd-control 3800/tcp open pwgpsi 3801/tcp open ibm-mgr 3809/tcp open apocd 3814/tcp open neto-dcs 3826/tcp open wormux 3827/tcp open netmpi 3828/tcp open neteh 3851/tcp open spectraport 3869/tcp open ovsam-mgmt 3871/tcp open avocent-adsap 3878/tcp open fotogcad 3880/tcp open igrs 3889/tcp open dandv-tester 3905/tcp open mupdate 3914/tcp open listcrt-port-2 3918/tcp open pktcablemmcops 3920/tcp open exasoftport1 3945/tcp open emcads 3971/tcp open lanrevserver 3986/tcp open mapper-ws_ethd 3995/tcp open iss-mgmt-ssl 3998/tcp open dnx 4000/tcp open remoteanything 4001/tcp open newoak 4002/tcp open mlchat-proxy 4003/tcp open pxc-splr-ft 4004/tcp open pxc-roid 4005/tcp open pxc-pin 4006/tcp open pxc-spvr 4045/tcp open lockd 4111/tcp open xgrid 4125/tcp open rww 4126/tcp open ddrepl 4129/tcp open nuauth 4224/tcp open xtell 4242/tcp open vrml-multi-use 4279/tcp open vrml-multi-use 4321/tcp open rwhois 4343/tcp open unicall 4443/tcp open pharos 4444/tcp open krb524 4445/tcp open upnotifyp 4446/tcp open n1-fwp 4449/tcp open privatewire 4550/tcp open gds-adppiw-db 4567/tcp open tram 4662/tcp open edonkey 4848/tcp open appserv-http 4899/tcp open radmin 4900/tcp open hfcs 4998/tcp open maybe-veritas 5000/tcp open upnp 5001/tcp closed commplex-link 5002/tcp open rfe 5003/tcp open filemaker 5004/tcp open avt-profile-1 5009/tcp open airport-admin 5030/tcp open surfpass 5033/tcp open unknown 5050/tcp open mmcc 5051/tcp open ida-agent 5054/tcp open rlm-admin 5060/tcp open sip 5061/tcp open sip-tls 5080/tcp open onscreen 5087/tcp open unknown 5100/tcp open admd 5101/tcp open admdog 5102/tcp open admeng 5120/tcp open unknown 5190/tcp open aol 5200/tcp open targus-getdata 5214/tcp open unknown 5221/tcp open 3exmp 5222/tcp open xmpp-client 5225/tcp open hp-server 5226/tcp open hp-status 5269/tcp open xmpp-server 5280/tcp open xmpp-bosh 5298/tcp open presence 5357/tcp open wsdapi 5405/tcp open pcduo 5414/tcp open statusd 5431/tcp open park-agent 5432/tcp open postgresql 5440/tcp open unknown 5500/tcp open hotline 5510/tcp open secureidprop 5544/tcp open unknown 5550/tcp open sdadmind 5555/tcp open freeciv 5560/tcp open isqlplus 5566/tcp open westec-connect 5631/tcp open pcanywheredata 5633/tcp open beorl 5666/tcp open nrpe 5678/tcp open rrac 5679/tcp open activesync 5718/tcp open dpm 5730/tcp open unieng 5800/tcp open vnc-http 5801/tcp open vnc-http-1 5802/tcp open vnc-http-2 5810/tcp open unknown 5811/tcp open unknown 5815/tcp open unknown 5822/tcp open unknown 5825/tcp open unknown 5850/tcp open unknown 5859/tcp open wherehoo 5862/tcp open unknown 5877/tcp open unknown 5900/tcp open vnc 5901/tcp open vnc-1 5902/tcp open vnc-2 5903/tcp open vnc-3 5904/tcp open unknown 5906/tcp open unknown 5907/tcp open unknown 5910/tcp open cm 5911/tcp open cpdlc 5915/tcp open unknown 5922/tcp open unknown 5925/tcp open unknown 5950/tcp open unknown 5952/tcp open unknown 5959/tcp open unknown 5960/tcp open unknown 5961/tcp open unknown 5962/tcp open unknown 5963/tcp open indy 5987/tcp open wbem-rmi 5988/tcp open wbem-http 5989/tcp open wbem-https 5998/tcp open ncd-diag 5999/tcp open ncd-conf 6000/tcp open X11 6001/tcp open X11:1 6002/tcp open X11:2 6003/tcp open X11:3 6004/tcp open X11:4 6005/tcp open X11:5 6006/tcp open X11:6 6007/tcp open X11:7 6009/tcp open X11:9 6025/tcp open x11 6059/tcp open X11:59 6100/tcp open synchronet-db 6101/tcp open backupexec 6106/tcp open isdninfo 6112/tcp open dtspc 6123/tcp open backup-express 6129/tcp open unknown 6156/tcp open unknown 6346/tcp open gnutella 6389/tcp open clariion-evr01 6502/tcp open netop-rc 6510/tcp open mcer-port 6543/tcp open mythtv 6547/tcp open powerchuteplus 6565/tcp open unknown 6566/tcp open sane-port 6567/tcp open esp 6580/tcp open parsec-master 6646/tcp open unknown 6666/tcp open irc 6667/tcp open irc 6668/tcp open irc 6669/tcp open irc 6689/tcp open tsa 6692/tcp open unknown 6699/tcp open napster 6779/tcp open unknown 6788/tcp open smc-http 6789/tcp open ibm-db2-admin 6792/tcp open unknown 6839/tcp open unknown 6881/tcp open bittorrent-tracker 6901/tcp open jetstream 6969/tcp open acmsoda 7000/tcp open afs3-fileserver 7001/tcp open afs3-callback 7002/tcp open afs3-prserver 7004/tcp open afs3-kaserver 7007/tcp open afs3-bos 7019/tcp open unknown 7025/tcp open vmsvc-2 7070/tcp open realserver 7100/tcp open font-service 7103/tcp open unknown 7106/tcp open unknown 7200/tcp open fodms 7201/tcp open dlip 7402/tcp open rtps-dd-mt 7435/tcp open unknown 7443/tcp open oracleas-https 7496/tcp open unknown 7512/tcp open unknown 7625/tcp open unknown 7627/tcp open soap-http 7676/tcp open imqbrokerd 7741/tcp open scriptview 7777/tcp open cbt 7778/tcp open interwise 7800/tcp open asr 7911/tcp open unknown 7920/tcp open unknown 7921/tcp open unknown 7937/tcp open nsrexecd 7938/tcp open lgtomapper 7999/tcp open irdmi2 8000/tcp open http-alt 8001/tcp open vcom-tunnel 8002/tcp open teradataordbms 8007/tcp open ajp12 8008/tcp open http 8009/tcp open ajp13 8010/tcp open xmpp 8011/tcp open unknown 8021/tcp open ftp-proxy 8022/tcp open oa-system 8031/tcp open unknown 8042/tcp open fs-agent 8045/tcp open unknown 8080/tcp open http-proxy 8081/tcp open blackice-icecap 8082/tcp open blackice-alerts 8083/tcp open us-srv 8084/tcp open unknown 8085/tcp open unknown 8086/tcp open d-s-n 8087/tcp open simplifymedia 8088/tcp open radan-http 8089/tcp open unknown 8090/tcp open unknown 8093/tcp open unknown 8099/tcp open unknown 8100/tcp open xprint-server 8180/tcp open unknown 8181/tcp open unknown 8192/tcp open sophos 8193/tcp open sophos 8194/tcp open sophos 8200/tcp open trivnet1 8222/tcp open unknown 8254/tcp open unknown 8290/tcp open unknown 8291/tcp open unknown 8292/tcp open blp3 8300/tcp open tmi 8333/tcp open bitcoin 8383/tcp open m2mservices 8400/tcp open cvd 8402/tcp open abarsd 8443/tcp open https-alt 8500/tcp open fmtp 8600/tcp open asterix 8649/tcp open unknown 8651/tcp open unknown 8652/tcp open unknown 8654/tcp open unknown 8701/tcp open unknown 8800/tcp open sunwebadmin 8873/tcp open dxspider 8888/tcp open sun-answerbook 8899/tcp open ospf-lite 8994/tcp open unknown 9000/tcp open cslistener 9001/tcp open tor-orport 9002/tcp open dynamid 9003/tcp open unknown 9009/tcp open pichat 9010/tcp open sdr 9011/tcp open unknown 9040/tcp open tor-trans 9050/tcp open tor-socks 9071/tcp open unknown 9080/tcp open glrpc 9081/tcp open unknown 9090/tcp open zeus-admin 9091/tcp open xmltec-xmlmail 9099/tcp open unknown 9100/tcp open jetdirect 9101/tcp open jetdirect 9102/tcp open jetdirect 9103/tcp open jetdirect 9110/tcp open unknown 9111/tcp open DragonIDSConsole 9200/tcp open wap-wsp 9207/tcp open wap-vcal-s 9220/tcp open unknown 9290/tcp open unknown 9415/tcp open unknown 9418/tcp open git 9485/tcp open unknown 9500/tcp open ismserver 9502/tcp open unknown 9503/tcp open unknown 9535/tcp open man 9575/tcp open unknown 9593/tcp open cba8 9594/tcp open msgsys 9595/tcp open pds 9618/tcp open condor 9666/tcp open unknown 9876/tcp open sd 9877/tcp open unknown 9878/tcp open unknown 9898/tcp open monkeycom 9900/tcp open iua 9917/tcp open unknown 9929/tcp open nping-echo 9943/tcp open unknown 9944/tcp open unknown 9968/tcp open unknown 9998/tcp open distinct32 9999/tcp open abyss 10000/tcp open snet-sensor-mgmt 10001/tcp open scp-config 10002/tcp open documentum 10003/tcp open documentum_s 10004/tcp open emcrmirccd 10009/tcp open swdtp-sv 10010/tcp open rxapi 10012/tcp open unknown 10024/tcp open unknown 10025/tcp open unknown 10082/tcp open amandaidx 10180/tcp open unknown 10215/tcp open unknown 10243/tcp open unknown 10566/tcp open unknown 10616/tcp open unknown 10617/tcp open unknown 10621/tcp open unknown 10626/tcp open unknown 10628/tcp open unknown 10629/tcp open unknown 10778/tcp open unknown 11110/tcp open unknown 11111/tcp open vce 11967/tcp open sysinfo-sp 12000/tcp open cce4x 12174/tcp open unknown 12265/tcp open unknown 12345/tcp open netbus 13456/tcp open unknown 13722/tcp open netbackup 13782/tcp open netbackup 13783/tcp open netbackup 14000/tcp open scotty-ft 14238/tcp open unknown 14441/tcp open unknown 14442/tcp open unknown 15000/tcp open hydap 15002/tcp open unknown 15003/tcp open unknown 15004/tcp open unknown 15660/tcp open bex-xr 15742/tcp open unknown 16000/tcp open fmsas 16001/tcp open fmsascon 16012/tcp open unknown 16016/tcp open unknown 16018/tcp open unknown 16080/tcp open osxwebadmin 16113/tcp open unknown 16992/tcp open amt-soap-http 16993/tcp open amt-soap-https 17877/tcp open unknown 17988/tcp open unknown 18040/tcp open unknown 18101/tcp open unknown 18988/tcp open unknown 19101/tcp open unknown 19283/tcp open keysrvr 19315/tcp open keyshadow 19350/tcp open unknown 19780/tcp open unknown 19801/tcp open unknown 19842/tcp open unknown 20000/tcp open dnp 20005/tcp open btx 20031/tcp open unknown 20221/tcp open unknown 20222/tcp open ipulse-ics 20828/tcp open unknown 21571/tcp open unknown 22939/tcp open unknown 23502/tcp open unknown 24444/tcp open unknown 24800/tcp open unknown 25734/tcp open unknown 25735/tcp open unknown 26214/tcp open unknown 27000/tcp open flexlm0 27352/tcp open unknown 27353/tcp open unknown 27355/tcp open unknown 27356/tcp open unknown 27715/tcp open unknown 28201/tcp open unknown 30000/tcp open unknown 30718/tcp open unknown 30951/tcp open unknown 31038/tcp open unknown 31337/tcp open Elite 32768/tcp open filenet-tms 32769/tcp open filenet-rpc 32770/tcp open sometimes-rpc3 32771/tcp open sometimes-rpc5 32772/tcp open sometimes-rpc7 32773/tcp open sometimes-rpc9 32774/tcp open sometimes-rpc11 32775/tcp open sometimes-rpc13 32776/tcp open sometimes-rpc15 32777/tcp open sometimes-rpc17 32778/tcp open sometimes-rpc19 32779/tcp open sometimes-rpc21 32780/tcp open sometimes-rpc23 32781/tcp open unknown 32782/tcp open unknown 32783/tcp open unknown 32784/tcp open unknown 32785/tcp open unknown 33354/tcp open unknown 33899/tcp open unknown 34571/tcp open unknown 34572/tcp open unknown 34573/tcp open unknown 35500/tcp open unknown 38292/tcp open landesk-cba 40193/tcp open unknown 40911/tcp open unknown 41511/tcp open unknown 42510/tcp open caerpc 44176/tcp open unknown 44442/tcp open coldfusion-auth 44443/tcp open coldfusion-auth 44501/tcp open unknown 45100/tcp open unknown 48080/tcp open unknown 49152/tcp open unknown 49153/tcp open unknown 49154/tcp open unknown 49155/tcp open unknown 49156/tcp open unknown 49157/tcp open unknown 49158/tcp open unknown 49159/tcp open unknown 49160/tcp open unknown 49161/tcp open unknown 49163/tcp open unknown 49165/tcp open unknown 49167/tcp open unknown 49175/tcp open unknown 49176/tcp open unknown 49400/tcp open compaqdiag 49999/tcp open unknown 50000/tcp open ibm-db2 50001/tcp open unknown 50002/tcp open iiimsf 50003/tcp open unknown 50006/tcp open unknown 50300/tcp open unknown 50389/tcp open unknown 50500/tcp open unknown 50636/tcp open unknown 50800/tcp open unknown 51103/tcp open unknown 51493/tcp open unknown 52673/tcp open unknown 52822/tcp open unknown 52848/tcp open unknown 52869/tcp open unknown 54045/tcp open unknown 54328/tcp open unknown 55055/tcp open unknown 55056/tcp open unknown 55555/tcp open unknown 55600/tcp open unknown 56737/tcp open unknown 56738/tcp open unknown 57294/tcp open unknown 57797/tcp open unknown 58080/tcp open unknown 60020/tcp open unknown 60443/tcp open unknown 61532/tcp open unknown 61900/tcp open unknown 62078/tcp open iphone-sync 63331/tcp open unknown 64623/tcp open unknown 64680/tcp open unknown 65000/tcp open unknown 65129/tcp open unknown 65389/tcp open unknown 
submitted by ThreshingBee to Kali_Linux_Essentials [link] [comments]

Get Unlimited HQ Proxies for Cracking Squid Proxy Autenticado LDAP COMO ATIVAR OU COLOCAR TOKEN NO MERCADO DE BTICOIN - YouTube Proxy server do not request for account and password but ... What Is Wrapped Bitcoin? (WBTC) - YouTube

Position of the Cookie = your Password) rpccookiefile=D:\Bitcoin\wallet.cookie . allow not needed i guess for you are allways free to connect in your network but i did it anyway rpcallowip=127.0.0.1. connection to the python proxy ( i use python-bitcoinrpc-master, much better then Python only. from bitcoinrpc.authproxy import AuthServiceProxy Auth ALERT! Click here to register with a few steps and explore all our cool stuff we have to offer! Jump to content. Home ... Bitcoin, Litecoin and many other alternative coins have become the currency these days. Discuss them in one place. 3,353; 62,253 [HQ Leak] 7 Must Read Crypt... 26 Oct, 2020 By chacha321; Entertainment. Talk about your favourite movies, series or listen to some music ... ## ## bitcoin.conf configuration file. Lines beginning with # are comments. ## # Network-related settings: # Run on the test network instead of the real bitcoin network. #testnet=0 # Run a regression test network #regtest=0 # Connect via a SOCKS5 proxy #proxy=127.0.0.1:9050 # Bind to given address and always listen on it. Use [host]:port ... from bitcoin. core. script import CScript, OP_DUP, OP_HASH160, OP_EQUALVERIFY, OP_CHECKSIG, SignatureHash, SIGHASH_ALL, SIGHASH_SINGLE, SIGVERSION_WITNESS_V0 import bitcoin. rpc import bitcoin What's the best way to specify a proxy with username and password for an http connection in python?

[index] [16437] [28670] [50837] [19094] [32144] [42044] [3800] [20854] [24839] [21537]

Get Unlimited HQ Proxies for Cracking

IT'S A PROXY THING ... #proxies #buffersitewizard #privateproxies In this video, I show you exactly which proxy provider I use on a regular basis (5 years +) and why ... REFERRED IN VIDEO https ... A demonstration of the new capability in IBM Integration Bus v10.0.0.9 which allows you to easily use an HTTP Forward Proxy server that has authentication en... To Join TRX Forsage My Referral Link: https://trx.forsage.io/auth/t/omhpyr/ Make Sure While Signing Up My Forsage ID: 94633 Should Be Displayed On Screen My ... Buy bitcoin with credit card no ID verification (4 ways) - Duration: 14:46. ... how to setup proxy authentication on android - Duration: 1:49. somnath sharma 3,182 views. 1:49. Proxy Settings For ... Neste vídeo eu mostro como recuperar token ou fazer token para entrar no mercado de bitcoin http://mmmbrasilgd.blogspot.com.br/ GANHE 50% NA SUA PRIMEIRA PRE...

#