Timekoin MantisBT - Issues

0000083: Low Memory Mode will prevent Transaction Clerk, Foundation Manager, Balance Indexer from running during Foundation repair

Sat, 11 Dec 2021 13:30:56 -0600

If the Timekoin server detects an issue with a foundation block, the repair process will stop after one repair cycle with low memory mode, this will also stop Transaction Clerk and Balance Indexer from running because they are waiting on the Foundation Manager to finish work in the database before processing their own queue of information.

0000080: Spell check on the generation tab description

Tue, 12 Oct 2021 20:30:06 -0500

""You may test you router/firewall settings using the Firewall Tool."" should be "You may test [your] router/firewall settings using the Firewall Tool." you >your

The server must be accessible from the Internet and be able to accept and respond to HTTP requests on the port designated in the System tab. This allows peer servers to validate the existence of your server. You may test you router/firewall settings using the Firewall Tool. If your server fails this test, you must modify your router or firewall settings to allow inbound TCP connections on your chosen port.

0000081: Feature Request: have transaction hash and details printed in successful transaction broadcast.

Tue, 07 Sep 2021 01:19:14 -0500

I know that transactions are not confirmed until the transaction cycle is submitted but if a transaction hashed is generated/produced at the time of submitting a transaction it should be printed for the client with the - send and receive key + the amount + the time + message (just like a payment receipt) so that the payer can provide a transaction ID to the seller ahead of the confirmation.

Next thing to add after this is the ability to search by transaction hash on the timekoin explorer app

0000078: Easy Key generation reports that key exists when creating new easy key

Wed, 25 Aug 2021 16:54:11 -0500

1.3 client install EasyKey generation claims key exists when trying to create

0000079: QR code generator for public key

Wed, 25 Aug 2021 14:22:14 -0500

Build in a QR code generator for public key so that payments can be accepted by scanning public key from the new app

0000074: Allow to key backups and restore via file downloads and upload

Wed, 18 Aug 2021 16:33:27 -0500

Instead of using copy/paste to backup and restore keys, have Timekoin create a simple text file with the keys already in it for download. Then, if the user needs to restore keys, they have the option of using the file to upload and restore. This can help eliminate errors or browser issues where the full key is not copied correctly for unknown reasons.

0000075: Allow to key backups and restore via file downloads and upload

Tue, 17 Aug 2021 03:14:51 -0500

0000076: Creating a new Easy Key at the exact same time as a Peer Election results in failure

Mon, 16 Aug 2021 23:55:13 -0500

If you create an Easy Key during the same cycle as a Peer Election is suppose to finish, it will fail because the new Peer that was just elected was not included in the round of payments to all the servers.

0000077: Permanent Peer Priority enabled with no Permanent Peers assigned blocks outbound Peer Polling

Sun, 15 Aug 2021 02:15:21 -0500

If you have Permanent Peer Priority enabled and no Permanent Peer assigned, the polling list of peers is blanked out because there has to be at least 1 Permanent Peer assigned to work properly.

0000073: New server with a blank transaction history database can disable Treasurer Processor

Fri, 13 Aug 2021 17:27:46 -0500

When starting Timekoin Server with a blank database, there is a 10 second test phase where the system checks if your system can produce properly encrypted transactions. Once that phase is over, it never runs again and begins to update the database via other online peers. During this 10 second phase, the Treasurer Processor is disabled so it doesn't interfere with the testing.

0000058: History Sent From does not list properly

Fri, 13 Aug 2021 16:32:41 -0500

When History is selected. The History for the Sent From server component are not displayed properly according to the number selected. The default is to display the last 5 transactions sent from the server, however, if the transaction from the server actually occurred 6 server transactions back it will cease to display.

0000071: Repair from Transaction Cycle# 0 results in wrong hash values afterwards

Wed, 12 Mar 2014 20:18:23 -0500

While in the Timekoin Server GUI, doing a Tools Tab, Repair Button for Transaction History from Transaction Cycle #0 results in incorrect hash values afterwards.

0000070: Peer list can overpopulate when logging in to client

Sat, 09 Nov 2013 11:08:23 -0600

The peer list can overpopulate when logging in to client.

0000053: Display how long until the next generation cycle

Fri, 25 Oct 2013 15:57:04 -0500

It took me a long time to figure out that you can not generate every cycle. I thought something was wrong with my server when it would not generate for 30 minutes or more. I know now that it is based on a randomly chosen cycle. Display when the next cycle is just like you do the election.

In fact, it might be good to put a link to the generation and election clocks you created in a previous post. I would put some info at the top explaining a bit more about generation/election and their random cycles and then display the data as you have it now. I would default it to 24 hours.

I think this would make it much easier to understand for the non-technical and new timekoin users.

0000069: Server Peers with dynamic IPs on Domain Names can get out of sync IPs with the generation IP

Fri, 25 Oct 2013 15:43:47 -0500

Peers with dynamic IPs using DNS names can get IPs out of sync, which can cause an issue if the peer is shutdown or goes offline. When the peer comes back online and submits an election request, the IPs may not match for reverse verification.

0000068: Transaction Foundation Manager can get stuck in a repair loop

Thu, 24 Oct 2013 04:02:23 -0500

The Transaction Foundation Manager can get stuck in a loop that tries to repair past foundations that are not damaged.

0000067: Balance cache can sometimes expire before it is updated from other peers

Tue, 22 Oct 2013 15:47:45 -0500

When navigating the client interface, the balance can come up as "NA" from time to time.

0000066: Line return characters can be saved into an easy key

Mon, 21 Oct 2013 15:26:55 -0500

Line return characters such as /n or /r can be saved into the data for easy keys causing them to not work in some clients.

0000065: Bug in Domain check variable in genpeer.php prevents peers from joining election queue

Thu, 17 Oct 2013 20:32:53 -0500

The $domain_fail variable is not being reset so if 2 peers are trying to join the queue for election and the first peer fails on a domain check, it makes the next peer fail if using IP only.

0000052: Notify the user that there is a software update

Wed, 16 Oct 2013 21:34:45 -0500

I only find out by stumbling across it on the download page.

0000064: Balance in GUI can be off in the negative or positive direction

Sun, 05 May 2013 00:51:59 -0500

The Balance displayed in the GUI can be off by a large amount in either direction (more or less).

0000063: 0 balance reports in the GUI

Mon, 15 Apr 2013 02:20:55 -0500

Even though network transactions are recorded properly, the balance in the GUI can still show up as 0 for some systems.

0000062: Windows computers can not get elected by the network

Fri, 12 Apr 2013 22:04:29 -0500

Windows OS computers can not get elected for currency generation.

0000059: Peers with no domain setup in the system tab will filter other peers using just IP address

Wed, 03 Apr 2013 23:50:36 -0500

I discovered this in regression testing, if a peer does not use a domain name (just using its own IP address), this causes a filter bug. The peer ends up filtering out other peers that are using IP only, but peers with domains will be included in the peer list and attempts to join other peers.

0000057: Transactions are refused with v2.33 due to filtering key bits bug.

Tue, 19 Mar 2013 00:46:09 -0500

Transactions fail in version 2.33 because the filtering key bit length for the keys is expecting bit sizes too big (bigger than 1,536 bits).