Help users find a place to move it.

Could also include a link to the coin light wallet if they have one.

Second column should be the full name of the coin (to prevent confusion)

Need to sync LBTC full node and deploy Node interface for full claims,

Or, find an explorer which can broadcast.

Users are reporting this error:

16: mandatory-script-verify-flag-failed (Signature must be zero for failed CHECK(MULTI)SIG operation)

This seems to be caused by an error in signatures (https://bitcointalk.org/index.php?topic=1680640.0)

The cause of the error must be investigated. It is probably in either the transaction input generation, or in signing. Possibly a rounding/conversion error somewhere.

This problem is likely caused by an out of date .NET framework. Needs to be validated, and ideally, the user should be presented with a solution instead of the error.

If the Community Jar cookie is deleted after having just done a withdraw, the website reverts to IP-based restriction.

In this mode, the countdown timer does not give the correct value.

Data exists for withdraw for sure.

Receiving this message:

parameter 1 must be hexadecimal string (not 'send') [Host: 127.0.0.1:9332 User:liteuser Using password:yes]. Code:-8

Adding a direct link to see the value of the claims in the forked coin explorers would help to provide information to users on where the fork values come from.

Segwit claims get message:

bad-txns-vin-empty

Some concern about the load this could have on multiple block searches...

Full node is online, need to hook up claims.

Add these statistics to show how much funds are moving within the jar.

• add a chart (daily volume?)
• add a chart (in/out?)

Possibly use a hover-able drop down?

https://www.w3schools.com/howto/howto_css_dropdown.asp

If there are any observations of a node down in a 6 hour bin, mark as red. Otherwise, green. No data = 0.

Need to rebuild signing tool for linux and ensure BTCP is enabled.

https://github.com/bitcoin-atom/bitcoin-atom

Can be prevented by detecting activity and banning node.

Implement new format.

E.g. see https://www.w3schools.com/js/js_date_formats.asp

make consistent.

search invoice history periodically?

Search the blockchain to see if the balance has already been spent.

Keep a record of the original value, and also record the updated value.

The table should have something like

The expandable can contain info on coin website, etc.

Any use of cookies is expressly stated on the page where they are in use.

Lots of old stale code is left in the codebase, need to clean it up.

Get data from an open API like https://api.coinmarketcap.com/v1/ticker/bitcoin/ ?

Add a page to look at the details of a LN transaction.

There is a new value for fwdinghistory called max_events. This should be set to 50000 on RPC.

Improve performance and responsiveness, and fewer errors that way.

submodule not correctly linked to github.

Pending available wallet funds, of course.

Maybe a voting window?

https://www.coinpanic.com/Lightning should give node name.

The information about the nodes should also be cached by the website to minimize the number or RPC calls to the lightning daemon.

Getting an error:

16: mandatory-script-verify-flag-failed (Script evaluated without error but finished with a false/empty top stack element)

for ubtc claim. cause unknown.

It would certainly add credibility to your service 👍