Well, I don't think mobile mining is going to work out so well.  While the hash algorithm does prevent just driving a battery to zero, it is still a load.  And your mobile device isn't likely to have a fast memory system, so I don't think you'd get much from it.

Monday is 17:00 UTC is coming fast!

If you want to get started mining, definitely join the PegNet Discord and talk through your plan!  You now have about 50 hours to get ready!

Just doing last minute documentation and cleanup for the launch of mining on Monday August 19.

Mining requires sources to pull data from, and now all default sources now are free data feeds are mostly free data feeds.  One costs $12 a month.

Always interested in more sources, so let us know if you have a lead on good real time market data that can be used by the PegNet Oracle Price Record Chain!

My mistake.  The members have to declare themselves as public.  There are 15 developers with commit rights on the project, and more that are contributing through pull requests.  Sorry about the confusion, and the original post has been updated.

If you go to PegNet.org you can follow the link to the discord, and all development is coordinated there.  I am what passes for the lead on the effort, and you can talk to me directly from the discord which I monitor pretty closely.  I am Paul Snow.

To answer your question, there is no FPGA support or work done on this hashing algorithm.

One would not expect an advantage to FPGA's with this miner... You are optimizing 10% of its execution (the computation). 90% of the execution time for this hash is waiting on DRAM to respond, and an FPGA can't make that faster.

One of the very interesting things about the LXRHash used by the PegNet is the fact that it does not target computation.

LXRHash targets the memory bottleneck.

Each byte of source data being hashed involves creating a complex state, and that state is created by xors and shifts, and random bytes selected from a 1 gb byte buffer.

In the end, the state is used to derive the resulting hash.

Because a random byte is selected intermittently in the computation of the state, the result is over 90% of the time used to compute the hash is waiting on memory.  As the largest cache on commercial processors is about 128 MB, the cache is nearly always blown, doing very little to speed up the hash.

Benefits of this for CPU mining:

• Computation takes only 10% of the time.  Driving computation to near zero with an ASIC only gets you a 10% boost in hash power
• When processors are waiting on memory, they are idle.  On an I7 running 8 LXRHash miners full blast, the power consumption only goes up 10 Watts .... roughly the draw of a LED light bulb
• The most effective mining hardware becomes Single Board Computers like the Raspberry Pi 4.  With 2 GB, the hardware cost per hash is half conventional hardware, likely a quarter or less of GPUs or ASICs

Because the target isn't computation, but the memory bandwidth to 1 GB of memory, the best way to improve hash power is to fix a fundamental limitation of all hardware:  I/O speed on and off chip.  So we don't have to worry about a new ASIC coming out that blows away CPU mining.  And when caches do become effective at 1 GB, we can increase the map to 2 GB, or 4 GB, or more.  So the hash can scale with hardware advancements.

LXRHash is a Proof of Work hash, not a cryptographic hash.  As such it has been evaluated for avalanche properties, and compared to Sha256 for  bits modified due to any change in the value being hashed.  Hash restarts don't work because it does a quick first past to initialize the state prior to the main loop.  Append attacks don't work because LXRHash does an additional pass over the 32 byte hash produced by the main loop.

The cryptographic hashing securing the PegNet come from Factom, and are based on Sha256 and Sha512.

This is more of a Bitcoin model than most projects.  The utility and functionality of providing many missing base pairs and providing conversion utility is driving investment to get listings and promotion.

So far the GitHub has 15 people, with about 15 or so non developers working on other tasks.

https://github.com/orgs/pegnet/people sorry, the people on a github project are not public outside the project. My mistake.

A new thread dawns.

I know that I have largely moved to the Factom slack, but will make a renewed commitment to follow this forum as well.   You guys were the first, and some of the most loyal supporters of Factom, and we are hugely thankful for you!  To that end, I've posted a Thanksgiving message to our larger forums and communities.  And that certainly includes this one!

The Factom Community is the bedrock of what we are doing. The input, the support, the observations, the critiques, the development even, etc. The community has been so incredibly wonderful, I cannot express how thankful I am simply by typing words.

We are going to do so much in the next year. And the community is what will be enabling us. I want to say, without a shadow of a doubt, we are so thankful to be on this road together with such great people.

As always, we're going to focus on what we do. Not just spewing words. But sometimes, you just have to say what you think and how you feel. A wonderful, restful, and energizing Thanksgiving to everybody, even those who technically are outside the US and not formally celebrating Thanksgiving.

You don't have to have government permission to be thankful!

Paul Snow
CEO Factom

We are taking down the Factom Network to deploy Factom Federation (M2).  Factom transactions  will not be processed for upto 24 hours.   

Just thought you all would like to know!

Paul

Entry credits are held around .1 cents.  There is an exchange rate, so they are not swapped 1 for 1.  At $3 an FCT, they are exchanged at 3000 Entry Credits for 1 FCT.

As the price goes up, fewer FCT are burned for the same activity in the protocol.  Once elections are in place, we grow the supply when the price goes up (fewer FCT are burned), and lower the supply (more FCT are burned) when the price goes down.  So the token is (eventually) self stabilizing.

The slack channel is run by the community for the community.  We at Factom are fully cooperating with Matthew, who set it up and brought us in.

We as always are anti-censorship, but the slack channel has some rules that will be enforced.  

We welcome the conversation!  One advantage of slack is channels, to let people read up on topics they care about, and ignore the rest!

Paul

We add federated servers, a key component to being a distributed autonomous protocol.  Right now the protocol is running on only our servers.

Right now this is kinda normal on many blockchains, including Factom.

That said, the Genesis code (some refer to as M1, the code you are running) is getting rather long in the tooth.  We are working to get Factom Federation out ASAP (what people cal M2), and you can take a preview of the new code by running a node on the Test Net now.   The new code base handles multiple federated servers for greater security and distributed authority.   We have vastly reduced the footprint in memory, use of CPU, and increases transaction rates.   The new code even has a nice control panel and built in explorer.

Paul

We would be interested in any information you have.  So if you can post or email the log messages, that would be great.  paul@factom.org would work. I don't know what we would be doing that would interfere with another coin's wallet and miner (other than with memory or cpu usage).  Also not sure why you would have to effectively delete the database and reload (what happens when you rename the ldb folder).

If you still have the ldb folder from your first attempt, it might be interesting to stop factomd, restore the old ldb folder, and restart factomd and see if that works.  It should.

Anyway, thanks so much for testing our system!

Paul

Depending on your connection, and the power of your machine, it can take a while to sync.  I some have reported a stall while downloading, so you can stop factomd and restart it. 

You can use your browser to monitor the progress.  On that computer, go to http://localhost:8090

Hope this helps.

We are pounding away on the Factom Federation (M2).  I'm feeling good about it.  The Test Net is holding up.  That said, we still have some work to do to make our release.  We are doing everything we can to release as soon as we **Safely** can do so.  No promise about schedules here.

Paul

Forgot what I was doing I think.  I'll not delete the thing, but I'm guessing I hit the wrong button somewhere along the way.

Paul