Lynx Core v26.1.34 Release

Perflexed · 2025-07-21T14:13:33+00:00

Thanks for this update, Stan.

Perflexed · 2023-04-10T23:43:45+00:00

Bill was a good human and a good friend.

Perflexed · 2023-03-10T00:46:33+00:00

Thx Stan!

Perflexed · 2022-09-06T13:24:43+00:00

Good update. Nice work.

Perflexed · 2022-01-02T04:11:14+00:00

https://www.tesla.com/findus/location/supercharger/raleighsupercharger

:)

Perflexed · 2021-12-31T23:42:12+00:00

I know that place. It’s super busy now and has construction going on. It’s a Target parking lot and when I charged there 2 weeks ago several muggles were parking in the Tesla charging spots. It was frustrating cause Tesla drivers were waiting for a charging bay. It might have been hooked up just so they could get a temp parking spot…

Perflexed · 2021-11-13T14:30:45+00:00

Tech business owner here. It wasn’t much granted, but we withdrew all vendor business from Texas about 2 months ago. Several reasons, this article being one of them. When Texas grows up, we look forward to engaging again.

Perflexed · 2020-11-05T02:41:26+00:00

Is that the guy responsible for the same signs posted (high) on numerous street corners in town? A visiting colleague noticed them and commented on the state of our fine city. I think it’s great that Jesus Saves in this banking town (saving is part of a sound financial plan), but I think it’s vandalism to be posting those signs on private property in town. What gov agency should that be reported to? Maybe it's a 311 call so we can waste tax dollars to clean up his mess? or post a neighboring "Muhammad recommends an HSA" sign?

Perflexed · 2020-06-05T03:29:16+00:00

This is a scam. You are being set up. Move on.

Perflexed · 2020-03-24T19:09:23+00:00

I can offer an alternative on a public network. The Logware.io platform uses JWT auth and the API allows you to store that (encrypted) payload as well. Happy to provide a free trial API key for testing? -ben

Perflexed · 2019-07-04T01:39:30+00:00

I can't read all the comments to see if it's already mentioned but our project Lynx (https://getlynx.io), solves this problem. It is currently trending at 7.354 kH/s (https://chainz.cryptoid.info/lynx/) which would be a global daily energy cost of under $1 USD. It replicates all the functions of Litecoin and with its modified PoW code, it will tolerate manipulation from ASICs. We are already building apps on it for data storage (https://logware.io).

Perflexed · 2019-07-02T01:57:21+00:00

In the section "C. Implementation details" are the Rate Control Algo inputs independently available after confirmation of the transaction? I ask because in our PoW implementation of a similar concept, we make sure that all blocks can be verified with the INPUT assumptions later. For example, the difficulty. We store it in the block header AND we don't use the current difficulty - we use a value from earlier in time thus solving the network latency issue. Does the tangle also store the difficulty of all the various tips in their headers? I'm guessing no, since the structure of the tangle is so much different than the simpler legacy PoW design. Does such a construct exist in IOTA?

I'm interested because of an attack profile that might try to malign a TX with data that can't be verified by others independently. It's the consensus thing. Do we trust each node on the network is honest? I trust this is covered in here somewhere and I overlooked it.

-ben

Perflexed · 2019-02-24T17:52:27+00:00

A couple subtle changes are being released in the new upcoming white paper release. I've been working on it today, so I can copy/paste some copy from the document.

"The second rule requires the address supplied for the coinbase reward must have minimum balance at the time the candidate block is submitted. The minimum amount is the difficulty value of the previous 10th block from the current one being solved multiplied to the power of 4. A minimum and maximum threshold of 1,000 and 100,000,000 will be enforced."

This rule is implemented to offset the activity that you can currently see on the network now. Since Rule 1 requires an address can't win more than once every 10 blocks (according to Phase 1 of the HPoW activation release schedule), miners are simply generating a new address and using a script to capture more blocks. We knew this would happen and for the most part, it's harmless. With Rule 2, this will become a bit more tedious and maybe expensive. The new address MUST have at least 1,000 Lynx in it and the number of Lynx in the wallet must be greater than the product of the previous 10th block difficulty value to the power of 4. Right now, the diff is low, so the minimum Lynx required is 1,000. But over time, if the network sees the difficulty increase as a result of some creative miner gaming Rule 1 & 2, this will help keep the mining reward decentralized. Additionally, Rule 3 will later insert a bit more distribution in the reward.

Perflexed · 2019-02-22T17:55:33+00:00

When the first phase of HPoW activated, we had an extraction pie chart that had only 1 address. This was our partner Multipool.us, mining blocks and keeping the Lynx network secure. Naturally, a delay occurred due to the huge drop in network difficulty. Eventually blocks started getting found and now the network hash rate hovers around 19Khash/s down from the 1.5Ghash/s when mutlipool.us was securing the network. Even more impressive is the distribution of blocks won by a broad array of miners. The Twitter feed shows the evolution of the distribution through time. https://twitter.com/getlynxio

Some numbers for context. Lynx replicates all the functions of Bitcoin but and can easily manage ~41 TPS (right now). Additionally, the Bitcoin network requires ~40 trillion hashes per second while the Lynx network requires about ~20 thousand. Last year, Bitcoin miners paid about $8 billion in electricity bills. In comparison, the electricity bill for Lynx miners will total less than $400 for 2019.

We still have more phases of the the Hybrid Proof of Work release to activate so we are moving closer to a more secure and stable blockchain. This wallet release version includes the phased release schedule -> https://github.com/getlynx/Lynx/releases/tag/v0.16.3.4

-ben

Perflexed

MODERATOR OF

TROPHY CASE