Goals

I'd like to offer up these goals for the network. What goals are missing? Please respond with your thoughts on how these goals are already met by an existing network, or how they could be met by a new network.
  1. Security of transactions. Uploaders, Downloaders, and Data Facilitators must be protected from their transactions.
    1. This goal must be maintained assuming some fraction of participating nodes are subversively working in collusion, and that all network traffic between participants is visible to the attacker.
    2. This is the highest priority and no compromise outside of the necessity for practicality will be made at the expense of this goal.
    3. Note, security from participation is NOT a goal. That is the goal of a darknet.
    4. Protection of Data Facilitators excludes the use of public exit points from the network. These serve as legal and technological attack points.
    5. Specific entry points for data should also be avoided. These also serve as legal and technological attack points.
  2. Anyone at anytime can participate in the network given a computer and Internet connection. It should be a public network, not a private darknet.
    1. Darknets require existing relationships with others already participating. This would exclude a large portion of the population that would like to participate but know of no other people already participating or willing to participate.
  3. Trust is dispersed over a user defined number of nodes.
    1. Trust is based on the probability that some faction of nodes known are NOT evil. This faction is defined by the user on a per access basis.
    2. The plain text of the transaction must not be revealed until it has passed through enough nodes that the user is comfortable with the probability it has passed through a trustworthy node as compared to the risk of the transaction.
    3. This is one of the biggest problems with many anonymous peer to peer networks. Requests and transactions are plain text to immediate nodes. The legal recourse is that you could simply be passing the request through from someone else. However, for some networks an immediate node could perform statistical analysis of the transactions to yield a fairly strong certainty of a user's general network activity.
  4. No centralization.
    1. Centralization is very tempting, especially given the previous goals. There are many benefits including performance, reliability, and security. However, centralization provides a small number of attack points to cripple or completely disable the entire network.
    2. Proper centralized servers can also be expensive, requiring solicitation for donations, or other money making schemes such as advertisements.

Tuesday, January 12, 2010

Good google..

This puts a great big smile on my face....

http://googleblog.blogspot.com/2010/01/new-approach-to-china.html
Posted by at 13 comments:

Tuesday, December 29, 2009

Phase 2 complete!

We've now finished our custom database. There should be substantial memory and performance improvements. Now we've moved onto the user interface (including the GUI). Hopefully, by the end of January we'll have the GUI completed and we'll be ready for our second launch.

Keep checking for updates! We're getting closer....
Posted by at No comments:

Monday, November 2, 2009


After 2 months and countless simulations and studies we've successfully implemented the new enhancements and bug fixes. Hello packets have been reduced by 85%, node queries have been reduced 99%, and data pushes have been reduced by 69%.

We even upgraded our simulation machine the “Pfyshtank” to an i7 920 with 6GB of dd3.

The performance and reliability enhancements are phenomenal. With a rapid node turnover rate of 15 days and nodes randomly off 45% of the time we still achieve almost 90% success for searches and downloads, and 99% success for uploads.

Now I'll move on to our custom database implementation! We'd still really like to find a solid developer for our GUI to help. Please email masequis – at – yahoo.com if you are interested.
Posted by at No comments:

Wednesday, September 30, 2009

God bless the EFF

Keep up the good work folks!!

http://www.eff.org/deeplinks/2009/09/prompted-eff-lawsuit-fbi-partially-releases-domest
Posted by at No comments:

Tuesday, August 25, 2009

Working on Pfyshnet again.

I've decided I'd just start working on Pfyshnet again despite not having a plan on building a base network of seed nodes. I hope that when we catch on I'll never have to worry about this again.

After stewing over Pfyshnet now for over a year, I've got some great ideas on how to improve network performance, bandwidth, and memory. To prove my theory about these being improvements though, I'm going to beef up the simulator and measure the current performance. Then when I do the improvements I can run the simulator to measure the improvement.

However, I realize I've forgotten a lot of the details about the implementaion. Therefore, my first task will be a code review. I'll also add some better documentation while I do this. I expect now that I have a fresh perspective I may find a few issues while I do this.

I expect the code review to take about 2 weeks or so, and then the simulator improvements probably a month. Then implementing the improvements will take another month or so. So maybe by Christmas time I'll be ready for another release.
Posted by at 2 comments:

Wednesday, October 22, 2008

Pfyshnet seed nodes are gone.

Our patron fell on hard times and has pulled the plug on the seed servers we were using for Pfyshnet. Pfyshnet requires at least 20 nodes to form the "base" of the network. Until we can achieve this again, Pfyshnet is down. If you are willing to run a full time node or can sponsor seed servers let us know. (masequis - at - yahoo - . - com)
Posted by at No comments:

Monday, September 15, 2008

Pfyshnet GUI released!!

Pfyshnet 0.0.8 has just been released!  Featuring our GUI!

Download and enjoy.

A bunch of folks are waiting for this release before trying out pfyshnet.  I'll ask that everyone be patient.  Please commit your node to running for a day or so.  Fast growth while the network is small will create some growing pains, but once a little stability forms, things should start working nicely!

If you don't already have a node, simply download the pfyshnet_bin_0.0.8.zip file fromhttp://pfyshnet.sourceforge.net/wiki/index.php/Downloads.  Unzip it.  Create a shortcut to the executable pfyshnet.jar file on your desktop.  Then double click!

You won't be able to use it for a period of time while it generates your node's keys.  This could take hours, or even up to a day depending on your hardware.  During this time you should disable “poll for return data” in Edit->Settings.  If you don't, you'll keep getting pop-up windows until your node has created its keys.

Once you start using the GUI, pay special attention to the little dot in the lower left corner.  When this icon is red, it indicates your node/gui is doing something.  You can submit requests during this time, but don't get impatient and submit the same request a bunch of times, or you'll just kill your node.

Also be careful with board updates.  If you submit too many board updates at once you'll swamp your node.  (the little dot will be red for a long time).  It will probably still work, but much slower.

If you have a node already, and want to upgrade.  Kill your node nicely (kill or Ctrl-C).  Then copy the new pfyshnet.jar file to your existing node installation.  Then restart your node.  Note: Both your node and the GUI will now be started with java -jar pfyshnet.jar.  If you just want to start the node, run like this:

  java -jar pfyshnet.jar -node

If your node is already running, and you just want the GUI, run like this:

  java -jar pfyshnet.jar -gui

NOTE: You must upgrade your node to use the GUI!  The GUI uses client features that did not exist in 0.0.7.

Lastly, we know the GUI still needs some work, but we think it's nicely usable for people to get started.  Please make note of bugs and feature requests.

Posted by at 1 comment:
Subscribe to: Posts (Atom)