Hey, if anyone is interested in being featured in an article that I'm writing, I'm looking to do a review of the Stellar protocol's implementation of the Lightning Network.

They recently released the beta for it on October 1st, 2018

Here's the GitHub below:

https://github.com/interstellar/starlight

Basically, would just like someone to 'mess around' with the network for a little bit.

Send some transactions back and forth. Attempt posting these TX to a testnet chain if the environment permits.

Get some screenshots, brief write-up on your findings.

I'll include you in part of a larger work that I am currently writing on the Stellar Networks' future implementation of the Lightning Network (by the end of Q4 2018).

The reason why I'm requesting this is because the LN implementation for #Stellar $XLM looks like it will work different than it would w $BTC

Here's the source for this information:

https://www.stellar.org/blog/lightning-on-stellar-roadmap/#future_work

If I understand correctly, Stellar is proposing implementing a system by which the state channel automatically updates itself so that the former channel states (tracked by the LN) cannot be published to the chain.

However, if that's the case then...I don't get the point of it.

I still believe that LN presents a counterparty risk since there is no mining or verification of said channels and everything instead relies on agreed upon values, HTLCs and potentially 'watchtower' (what makes them immune to bribing?) contracts on the regular Bitcoin protocol.

Looks like Stellar is attempting to create their own 'twist' or version of LN.

Again, I'm not sure. The federated consensus that $XLM has already creates a scalable chain (albeit not decentralized; but since they're targeting institutions, this probably won't be a major issue)

In the Stellar chat as we speak, looking for more information about LN and the purpose for its integration.

Hopefully I can get Jed's response / explanation on this

I've already spoken with Jed before on there - he's fairly responsive.

So, I anticipate I'll get an answer soon.

That's why, preferably, the LN environment is launched beforehand.

Not a super substantive conversation we had before obviously, but he is there and he does respond.

Not entirely sure what's going on with the Oyster protocol right now or where the fire is at, but there's definitely an issue a-brewing:

https://twitter.com/OysterProtocol/status/1056982361378902022

Wow... the "Hacker" was able to manipulate the smart contract of #PRL. He printed 4 million coins more, increasing the Supply. He then activated the Crowdsale function and bought the new tokens at ICO price. He sent them to Kucoin and dumped them all in about 15m.

https://etherscan.io/address/0x0001ee57bb28415742248d946d35c7f87cfd5a54

I haven't verified any portion of that information, but from what I've seen from a few sources, that appears to be the case.

I will amend/redact that should this turn out to be untrue.

#Oyster $PRL

Official statement from the Oyster team:

https://twitter.com/OysterProtocol/status/1056992312608342017

Brief Announcement: I just want to urge everyone in this space to be as safe as possible.

There is a deranged individual going around the cryptospace right now attempting to "dox" any and everyone that 'speaks out' against Bitfinex.

I'm not sure what their agenda is, but their behavior seems a bit psychotic and obsessed. I have reached out to Bitfinexed and a few others personally to urge them to take proper precautions to ensure their safety.

If you're in the United States, it's probably no secret that there's been an escalating level of mass violence over the past few months. I'm not sure what's going on, but I want everyone in this space to be safe.

We aren't going to stop doing what we're doing, but I wanted to let everyone know now publicly that I am receiving multiple, continued death threats on my life as well as the lives of my family members.

I have been in direct contact with the Federal Bureau of Investigation (FBI) [in person] and I'm optimistic that they'll be able to get to whoever this is before this starts getting dangerous. I'm truly worried for some people in this space and I sincerely hope that this does not rise to a level where people end up getting killed in this space.

I don't want to spread rumors, but I have it on very good intel that this 'ThinkExclamation!' person's 'dox' victims are supposed to be part of some 'public hit list'.

Again, I don't know this for sure - but when you combine the ferocious, obsessive and psychopathic behavior of this individual with the other death threats, stalking & hack attempts that myself and others have received, it really makes you wonder.

As I said above ^ you really can't take anything for granted. We saw what happened during the Las Vegas shootings, the Orlando nightclub, down in Texas etc.

There are a few people in this cryptospace that are obviously not mentally well and there's no telling how far that they will carry this obsession.

So, before any of you all decide to take your own stands and put out any factual information you have or blow the whistle, be safe. There's a really nasty, violent element in this cryptospace that's brewing right now and I'm afraid one of these lunatics are going to hurt someone before it's over with.

Hopefully the federal authorities can get to these people before they actually get to someone.

New article of course.

Last time we address this manic, crazed and deranged behavior:

https://blog.zerononcense.com/2018/10/29/theres-a-deranged-lunatic-stalking-popular-cryptocurrency-personalities

https://medium.com/oysterprotocol/oyster-update-b813390ce10e

Concerning the $PRL (inside job?) that occurred earlier today

Not sure if you all have heard of Andre Cronje, but this guy is a legend in the crypto space when it comes to dissecting and analyzing the technical underpinnings of projects (proud to have the honor to collab with him on some cool stuff coming up).

He knew that there was this latent possibility for exploit in Oyster months ago

Here's the original message he sent about that: