View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
83 [Timekoin Server] General Issue major always 2021-12-09 14:40 2021-12-11 13:30
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: high OS Version:  
Status: resolved Product Version: 4.21  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 4.22  
    Target Version: 4.22  
Summary: Low Memory Mode will prevent Transaction Clerk, Foundation Manager, Balance Indexer from running during Foundation repair
Description: 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.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000097)
KnightMB   
2021-12-09 14:41   
The current work-around is to disable Low Memory mode until this is fixed in the next version.
(0000098)
KnightMB   
2021-12-11 13:30   
Simple fix for complex issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
80 [Timekoin Server] General Issue text always 2021-09-05 08:46 2021-10-12 20:30
Reporter: jambo58 Platform: Linux  
Assigned To: KnightMB OS: Linux  
Priority: low OS Version: 20  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 4.21  
    Target Version:  
Summary: Spell check on the generation tab description
Description: ""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.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000088)
KnightMB   
2021-09-05 12:37   
I bet that error has been there for over 10 years, LOL.
(0000090)
KnightMB   
2021-10-12 20:30   
Spelling error corrected.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
81 [Timekoin Client] Feature Request minor have not tried 2021-09-07 01:15 2021-09-07 01:19
Reporter: jambo58 Platform: Any - Mobile or Desktop  
Assigned To: OS: Windows, Linux, iOS, Android  
Priority: normal OS Version:  
Status: new Product Version: 1.31  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Feature Request: have transaction hash and details printed in successful transaction broadcast.
Description: 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
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000089)
jambo58   
2021-09-07 01:19   
ie TLDR in addition to the "You just sent ## TK to the above public key.
Your balance will not reflect this until the transaction is recorded across the entire network."

Block: Sending Key
Block: Recipient Key
Block: Transaction Hash
Block: Amount
Block: date and time
Block:

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
78 [Timekoin Client] General Issue major always 2021-08-21 22:35 2021-08-25 16:54
Reporter: jambo58 Platform: Downloaded EXE client  
Assigned To: KnightMB OS: Windows 10  
Priority: high OS Version: 21h2  
Status: resolved Product Version: 1.3  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.31  
    Target Version: 1.31  
Summary: Easy Key generation reports that key exists when creating new easy key
Description: 1.3 client install EasyKey generation claims key exists when trying to create
Tags:
Steps To Reproduce: Create Easy Key using client 1.3 on windows (from the client EXE bundle)
Additional Information:
Attached Files: Screenshot 2021-08-25 230735.jpg (110,001 bytes) 2021-08-25 08:08
https://timekoin.net/mantisbt/file_download.php?file_id=5&type=bug
jpg

Screenshot 2021-08-25 230858.jpg (28,197 bytes) 2021-08-25 08:09
https://timekoin.net/mantisbt/file_download.php?file_id=6&type=bug
jpg
Notes
(0000079)
KnightMB   
2021-08-22 00:09   
Is it reporting an Easy Key exist when none should be?
(0000080)
jambo58   
2021-08-25 07:58   
correct i can do a screen recording to reproduce the issue for you
(0000082)
jambo58   
2021-08-25 08:08   
(0000083)
jambo58   
2021-08-25 08:09   
(0000084)
KnightMB   
2021-08-25 13:57   
Was able to confirm that easy key does not currently exist despite it showing that it is.
(0000085)
KnightMB   
2021-08-25 14:03   
Was able to reproduce. Wow, I can't believe that just broke at release. I'm sure it's a simple logic error, like the Easy Key is available but the bit is flipped the wrong way, so it thinks it's not. Should be an easy fix.
(0000087)
KnightMB   
2021-08-25 16:54   
The fix was a simple missing "0" of all things. Basically, when it checks if your new key exist already, the network will either return the full key (if it existed) or a simple 0 to represent no key exist by that name. The code was checking for a blank response instead of just the plain 0. Blank response is not reliable because if the network doesn't respond, even if the key did exist, would also be blank. The zero is a real response to check against and should be fixed in the next minor release.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
79 [Timekoin Client] Feature Request trivial N/A 2021-08-25 07:57 2021-08-25 14:22
Reporter: jambo58 Platform: timekoin.net/tkbillfold  
Assigned To: OS:  
Priority: low OS Version:  
Status: new Product Version: 1.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: QR code generator for public key
Description: Build in a QR code generator for public key so that payments can be accepted by scanning public key from the new app
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000081)
jambo58   
2021-08-25 08:03   
possible existing solution to retrofit

https://github.com/endroid/qr-code
(0000086)
KnightMB   
2021-08-25 14:22   
Thanks for the link, will research later as it would be very useful!

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
74 [Timekoin Client] Feature Request feature N/A 2021-08-13 17:15 2021-08-18 16:33
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.26  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.3  
    Target Version: 1.3  
Summary: Allow to key backups and restore via file downloads and upload
Description: 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.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000078)
KnightMB   
2021-08-18 16:33   
Added to version 1.3

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
75 [Timekoin Server] Feature Request feature N/A 2021-08-13 17:22 2021-08-17 03:14
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 4.13  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 4.15  
    Target Version: 4.15  
Summary: Allow to key backups and restore via file downloads and upload
Description: 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.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000077)
KnightMB   
2021-08-17 03:14   
Feature now available in v4.15 and higher

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
76 [Timekoin Server] General Issue minor always 2021-08-14 14:16 2021-08-16 23:55
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 4.13  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 4.15  
    Target Version: 4.15  
Summary: Creating a new Easy Key at the exact same time as a Peer Election results in failure
Description: 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.
Tags:
Steps To Reproduce: Wait until the same transaction cycle as the Peer election is suppose to finish and then create a new Easy Key.
Additional Information: Basically a logic timing issue.
Attached Files:
Notes
(0000072)
KnightMB   
2021-08-14 14:16   
I was able to confirm it by creating a new Easy Key at the same time that a Peer was to be elected.
(0000073)
KnightMB   
2021-08-14 14:17   
Should be an easy fix, if you try to create a Easy Key at the exact same time as the Peer Election, just have it queue to wait until the next cycle when the new Peer will be in the Generation List.
(0000074)
KnightMB   
2021-08-15 01:33   
Just added an election check to prevent creation right before a peer election and a message to the user to wait on the creation. Having an automated system to check the election status and submit between elections is beyond the current schedule scope to get this release out for the speed benefits and more important bug fixes.
(0000076)
KnightMB   
2021-08-16 23:55   
Timekoin will attempt to fit an Easy Key creating transaction in before any election is suppose to finish. If it's too close to predict (especially if multiple servers are in the queue to be elected), it will return error and tell the user to wait until the election has passed to try again.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
77 [Timekoin Server] General Issue major always 2021-08-15 01:41 2021-08-15 02:15
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: high OS Version:  
Status: resolved Product Version: 4.13  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 4.14  
    Target Version: 4.14  
Summary: Permanent Peer Priority enabled with no Permanent Peers assigned blocks outbound Peer Polling
Description: 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.
Tags:
Steps To Reproduce: Start Timekoin, enable Permanent Peer Priority, don't have any Permanent Peer(s) assigned in your Peerlist Tab.
You will see errors in the logs like "No Active Peers to Poll" constantly.
Additional Information: Permanent Peer Priority just polls your chosen peers ahead of the other peers first.
Attached Files:
Notes
(0000075)
KnightMB   
2021-08-15 02:15   
Using a union SQL statement to make the setting work if you have a permanent peer assigned or not when enabled.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
73 [Timekoin Server] General Issue major always 2021-08-13 17:00 2021-08-13 17:27
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 4.13  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 4.14  
    Target Version: 4.14  
Summary: New server with a blank transaction history database can disable Treasurer Processor
Description: 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.
Tags:
Steps To Reproduce: If you stop Timekoin within this 10 second window, the Treasurer Processor becomes stuck disabled. Even if you stop and restart the system, it remains stuck disabled.
Additional Information: This is rare but I had it happen to me by accident, so that means it could happen to anyone else.
The manual fix is to access and edit the "status.php" file and change the "TREASURER_DISABLED" from 1 to 0. That will enable it again for the system. The process is normally enabled after a successful test, but if you interrupt the test, it won't ever turn it back on since the test failed in live process.
Attached Files:
Notes
(0000071)
KnightMB   
2021-08-13 17:27   
Process changed to fix issue so the entire system is put on pause instead of just the Treasurer Processor, which means if anything did go wrong, and stop and restart would fix the issue. Lesson learned, don't rapid fire starting and stopping your new system for fun!

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
58 [Timekoin Server] General Issue minor always 2013-03-25 21:11 2021-08-13 16:32
Reporter: dangermouse Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2.34  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.35  
    Target Version: 2.41  
Summary: History Sent From does not list properly
Description: 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.
Tags:
Steps To Reproduce: Click History Tab and have a Sent From transaction more than 5 transactions back
Additional Information: SQL statement can be adjusted to make it work properly:

change statement from:

$sql = "SELECT timestamp, public_key_from, public_key_to, crypt_data3 FROM `transaction_history` WHERE `public_key_from` = '$my_public_key' ORDER BY `transaction_history`.`timestamp` DESC LIMIT $show_last";

to

$sql = "SELECT timestamp, public_key_from, public_key_to, crypt_data3 FROM `transaction_history` WHERE `public_key_to` != '$my_public_key' AND `public_key_from` = '$my_public_key' ORDER BY `transaction_history`.`timestamp`
DESC LIMIT $show_last";
Attached Files: screenshot_1.png (80,633 bytes) 2021-08-13 16:32
https://timekoin.net/mantisbt/file_download.php?file_id=4&type=bug
png
Notes
(0000048)
KnightMB   
2013-04-03 23:49   
I'll look into this, I don't know how I missed this bug report. I usually get an e-mail about them otherwise I would have responded sooner. :)
(0000050)
KnightMB   
2013-04-04 00:12   
(Last edited: 2013-04-04 00:13)
I attached a screen-shot of the test I did with v2.34, I had it show the last 7 transactions sent from the test machine. When you try something similar, basically it comes up blank?

(0000055)
KnightMB   
2013-04-04 01:08   
Ok, I see it now. If you have less than 5 sent transactions, you have to show 6 or more to get the past transactions to show. If you set 5, it only showed 1 in my test, when I really had 2 that should have showed up.
(0000056)
KnightMB   
2013-04-04 02:20   
Originally, the script would filter out the keys for the list to help speed things up, but that was probably before the indexes were introduced. So it has probably been broken for a while, but should be fixed now with the changes you recommended.
(0000070)
KnightMB   
2021-08-13 16:32   
This was the original screen-shot, restore from an earlier version.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
71 [Timekoin Server] General Issue major always 2014-03-12 16:14 2014-03-12 20:18
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 3.48  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 3.49  
    Target Version: 3.49  
Summary: Repair from Transaction Cycle# 0 results in wrong hash values afterwards
Description: 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.
Tags:
Steps To Reproduce:
Additional Information: Doing a repair from Transaction Cycle #0 does not use the B attribute transaction to build from, so the hash values afterwards are all incorrect.
Attached Files:
Notes
(0000067)
KnightMB   
2014-03-12 20:18   
Repair started at Cycle #0 fixed to do proper hash repair in the database from that point to the end of the database.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
70 [Timekoin Client] General Issue minor always 2013-11-09 11:07 2013-11-09 11:08
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.2  
    Target Version: 1.2  
Summary: Peer list can overpopulate when logging in to client
Description: The peer list can overpopulate when logging in to client.
Tags:
Steps To Reproduce: Remove all active peers, log out, log back in.
Additional Information:
Attached Files:
Notes
(0000066)
KnightMB   
2013-11-09 11:08   
Peer counting error would connect every peer in the reserve list instead of stopping at the limit set by the user.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
53 [Timekoin Server] Feature Request minor N/A 2013-03-02 16:34 2013-10-25 15:57
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2.21  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.43  
    Target Version: 2.3  
Summary: Display how long until the next generation cycle
Description: 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.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000065)
KnightMB   
2013-10-25 15:57   
Info added to Generation Tab

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
69 [Timekoin Server] General Issue minor random 2013-10-25 14:42 2013-10-25 15:43
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2.42  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.43  
    Target Version: 3.04  
Summary: Server Peers with dynamic IPs on Domain Names can get out of sync IPs with the generation IP
Description: 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.
Tags:
Steps To Reproduce: Generation IP field in the Generation Tab mismatch to what your real server IP address is.
Additional Information:
Attached Files:
Notes
(0000064)
KnightMB   
2013-10-25 15:43   
System tab now has a new configuration option for "Auto Generation IP Update". This will have the server poll it's public IP address randomly about every 10 to 30 minutes and if a change is detected due to dynamic IP address, update the Generation IP address field automatically.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
68 [Timekoin Server] General Issue major random 2013-10-23 23:33 2013-10-24 04:02
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: high OS Version:  
Status: resolved Product Version: 2.41  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.42  
    Target Version: 2.42  
Summary: Transaction Foundation Manager can get stuck in a repair loop
Description: The Transaction Foundation Manager can get stuck in a loop that tries to repair past foundations that are not damaged.
Tags:
Steps To Reproduce: It is very hard to replicate, but the circumstances requires that a peer is doing a routine transaction foundation compare with peers and mistakes a certain foundation block as "bad" and wipes/repairs it afterwards.
Additional Information: This can happen with a database error, but once it happens, it starts kind of a never ending cycle of repair that keeps the peer from being in sync with all other peers until all the server software is stopped and then restarted.
Attached Files:
Notes
(0000063)
KnightMB   
2013-10-24 04:02   
There was a variable not being reset properly that causes the loop, once this issue was fixed, the problem was resolved.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
67 [Timekoin Client] General Issue minor random 2013-10-22 12:29 2013-10-22 15:47
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.0  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.1  
    Target Version: 1.0  
Summary: Balance cache can sometimes expire before it is updated from other peers
Description: When navigating the client interface, the balance can come up as "NA" from time to time.
Tags:
Steps To Reproduce: Normal client usage
Additional Information:
Attached Files:
Notes
(0000062)
KnightMB   
2013-10-22 15:47   
Rework how the client handles 0 balances because a "non" response from a peer can also be considered zero just like a real zero response can.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
66 [Timekoin Easy Key] (No Category) minor always 2013-10-21 15:26 2013-10-21 15:26
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.21  
    Target Version: 1.21  
Summary: Line return characters can be saved into an easy key
Description: 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.
Tags:
Steps To Reproduce: Put a line return in the public key before submitting.
Additional Information:
Attached Files:
Notes
(0000061)
KnightMB   
2013-10-21 15:26   
Line returns and HTML tags are filtered now.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
65 [Timekoin Server] General Issue major random 2013-10-17 19:29 2013-10-17 20:32
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: high OS Version:  
Status: resolved Product Version: 2.4  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.41  
    Target Version: 2.41  
Summary: Bug in Domain check variable in genpeer.php prevents peers from joining election queue
Description: 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.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000060)
KnightMB   
2013-10-17 20:32   
Variable is reset properly to prevent this issue from occurring.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
52 [Timekoin Server] Feature Request minor N/A 2013-03-02 16:33 2013-10-16 21:34
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2.21  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.4  
    Target Version: 2.3  
Summary: Notify the user that there is a software update
Description: I only find out by stumbling across it on the download page.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000059)
KnightMB   
2013-10-16 21:34   
Daily check feature added.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
64 [Timekoin Server] Operating System Issue major random 2013-04-18 20:28 2013-05-05 00:51
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS: Windows  
Priority: high OS Version:  
Status: resolved Product Version: 2.37  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.4  
    Target Version: 2.4  
Summary: Balance in GUI can be off in the negative or positive direction
Description: The Balance displayed in the GUI can be off by a large amount in either direction (more or less).
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
63 [Timekoin Server] General Issue major random 2013-04-15 02:20 2013-04-15 02:20
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: high OS Version:  
Status: resolved Product Version: 2.36  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.37  
    Target Version: 2.37  
Summary: 0 balance reports in the GUI
Description: Even though network transactions are recorded properly, the balance in the GUI can still show up as 0 for some systems.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000058)
KnightMB   
2013-04-15 02:20   
When OpenSSL fails to decrypt a balance, the built-in RSA code for Timekoin will step in and attempt to decrypt the data.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
62 [Timekoin Server] Operating System Issue major random 2013-04-12 22:03 2013-04-12 22:04
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS: Windows  
Priority: high OS Version:  
Status: resolved Product Version: 2.35  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.36  
    Target Version: 2.36  
Summary: Windows computers can not get elected by the network
Description: Windows OS computers can not get elected for currency generation.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000057)
KnightMB   
2013-04-12 22:04   
This is due the way the first crypt1 field is being encrypted. The other peers can not decrypt it (and thus fails verification testing and is discarded). The issue seems to happen to certain keys that OpenSSL can not decrypt for.

The solution is to have a double-check during the decryption function. If OpenSSL can not decrypt the data, the built-in RSA code will take over and attempt to decrypt the data instead.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
59 [Timekoin Server] General Issue minor always 2013-04-03 23:48 2013-04-03 23:50
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: high OS Version:  
Status: resolved Product Version: 2.34  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.35  
    Target Version: 2.34  
Summary: Peers with no domain setup in the system tab will filter other peers using just IP address
Description: 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.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000049)
KnightMB   
2013-04-03 23:50   
The filter test to keep a peer from assigning itself via domain name did not take into account that a blank domain name (from itself) would also filter this from other peers using IP only (thus no domain field).

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
57 [Timekoin Server] General Issue major always 2013-03-19 00:44 2013-03-19 00:46
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: high OS Version:  
Status: resolved Product Version: 2.33  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.34  
    Target Version: 2.34  
Summary: Transactions are refused with v2.33 due to filtering key bits bug.
Description: 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).
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000047)
KnightMB   
2013-03-19 00:46   
Key filter fixed.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
56 [Timekoin Server] General Issue minor always 2013-03-15 12:45 2013-03-15 12:46
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: low OS Version:  
Status: resolved Product Version: 2.32  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.33  
    Target Version: 2.41  
Summary: Generation Peer Manager does repeated updates to IP address field for Generating Peers
Description: When changing your IP address that is recorded for the generation peer list, your own IP is recorded and updated over and over as seen in the logs. The update is successful, just not necessary to keep dinging the database with an update every 10 seconds to save it.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000046)
KnightMB   
2013-03-15 12:46   
More intelligent "once" update fixed if the database is already up to date with the IP address.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
55 [Timekoin Server] General Issue minor always 2013-03-14 11:01 2013-03-14 11:02
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2.31  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.32  
    Target Version: 2.32  
Summary: Queue Clerk refusing to accept inbound direct generation transactions
Description: Queue Clerk will accept direct inbound transactions, but ignores generation transactions.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000045)
KnightMB   
2013-03-14 11:02   
Queue Clerk was missing the attribute check for generation type "G", was only looking for type "T" for regular transactions before.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
54 [Timekoin Easy Key] General Issue minor always 2013-03-13 19:50 2013-03-13 19:51
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: low OS Version:  
Status: resolved Product Version: 1.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.2  
    Target Version: 1.2  
Summary: Data other than public keys can be saved as an easy key
Description: Someone can create easy keys that consist of only a single letter or word that has nothing to do with Timekoin.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000044)
KnightMB   
2013-03-13 19:51   
String lengths are checked on both the easy key input as well as the public key that a user is trying to assign to it.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
51 [Timekoin Server] General Issue minor random 2013-02-22 20:46 2013-02-22 21:35
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: high OS Version:  
Status: resolved Product Version: 2.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.21  
    Target Version: 2.21  
Summary: Generation Peer List does not filter duplicate election dates
Description: The generation peer manager does not filer duplicate election dates on public keys. So for example, you could have two different public keys with the same election time, which should not be possible as only one public key is ever elected during an election event.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000043)
KnightMB   
2013-02-22 21:35   
Both duplicate public key and election time are now checked when building the generation peer list.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
50 [Timekoin Server] General Issue minor random 2013-02-02 19:04 2013-02-02 19:49
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2.0  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.01  
    Target Version: 2.01  
Summary: Blank peers show up in Reserve Peer List
Description: When using a high setting for the number of Reserve Peer List to use, you will often see blank entries with no IP or Domain name. The entries take up space that could be used for real reserve peers.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000042)
KnightMB   
2013-02-02 19:49   
There appears to be no filtering for blank fields for IP & Domain at the same time instead of one or the other. Both blank field checking has been added that resolves the issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
49 [Timekoin Server] General Issue minor random 2013-01-31 10:37 2013-02-02 01:15
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: low OS Version:  
Status: resolved Product Version: 1.95  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.0  
    Target Version: 2.0  
Summary: Same peer shows up more than once in peer list
Description: Sometimes a peer will show up twice in the peer list, usually from Timekoin connecting out to new peers and using the same already connected peer twice.
Tags:
Steps To Reproduce:
Additional Information: The extra peers will eventually timeout because they don't get a heartbeat update, so eventually the peer will fall off the list.
Attached Files:
Notes
(0000041)
KnightMB   
2013-02-02 01:15   
A database call to check for duplicates was looking at the wrong field when the peer was set as a "permanent peer", thus showing up twice due to another connection made to the remote peer.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
48 [Timekoin Server] Performance Issue minor always 2012-12-04 22:54 2012-12-04 22:56
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: high OS Version:  
Status: resolved Product Version: 1.9  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.95  
    Target Version: 1.95  
Summary: Crypto Balance Index / Check Can Take too Long on Slower Machines
Description: Slower computers may not be able to process large balances for certain keys due to lower end hardware. This can cause them to ignore doing transactions for keys with large balances due to script timeout.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000040)
KnightMB   
2012-12-04 22:56   
Crypto balance checking was re-examined and optimized to run faster. Should see over a 300% speed increase in low end hardware running Timekoin server.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
47 [Timekoin Server] New Feature minor N/A 2012-08-13 22:09 2012-08-13 22:09
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.9  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.9  
    Target Version: 1.9  
Summary: Check and Repair Entire Database buttons added to the Tools tab
Description: The Check Database and Repair Database buttons were added to the Tools tab in the Web GUI of Timekoin. This will allow the user to execute database commands to check data integrity or repair damaged tables in the database without having to login and use the database console manually.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
46 [Timekoin Server] General Issue minor random 2012-08-10 13:30 2012-08-12 13:58
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.8  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.9  
    Target Version: 1.9  
Summary: Re-Building Transaction Foundation #0 Can Start a Loop that will Never Finish
Description: If Timekoin has to re-build Transaction Foundation Block #0 (the very first one) due to damage or corruption, it can become stuck in a loop. During the purge process, the very first beginning transaction is wiped and not rebuilt during the repair process and thus will never be built properly.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000038)
KnightMB   
2012-08-10 13:30   
Was able to reproduce on test machine.
(0000039)
KnightMB   
2012-08-12 13:58   
Foundation.php was the source of the problem, as it will wipe the "Beginning" transaction when doing a repair for Transaction Foundation Block #0. It has been modified to make an exception for the beginning transaction to avoid this situation of a repair loop that will never finish.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
45 [Timekoin Server] New Feature minor have not tried 2012-08-03 16:28 2012-08-03 16:30
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.8  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.8  
    Target Version: 1.8  
Summary: Ambient Peer Restart added to System Tab
Description: Ambient Peer Restart allows ambient peer polling to activate random checks of the Timekoin processor and Watchdog to ensure they are actually running. If a time variance of idle time is too high, the peerlist.php script will attempt to restart both Timekoin and the Watchdog due to this ambient peer traffic. This will allow Timekoin to function through Web Server restarts or Time Updates that cause Web Server restarts without warning.

This only works for peers that are Internet connected as it takes incoming peer traffic to trigger the random checks.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
17 [Timekoin Server] Performance Issue minor sometimes 2012-06-23 22:45 2012-08-03 16:24
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.5  
    Target Version: 1.3  
Summary: New Timekoin servers take too long to update transaction history
Description: A fresh timekoin server is suppose to start at record 4 (after the beginning record and the 3 test records for verification) and work it's way towards the end using the other peers as a way to build up the transaction history. Instead, the new timekoin server might jump right to the end and begin building the transaction history from the front instead (working backwards), which takes a lot more time.
Tags:
Steps To Reproduce: Start a new timekoin server where the transaction history is empty.
Additional Information:
Attached Files:
Notes
(0000012)
KnightMB   
2012-06-23 22:47   
I was able to reproduce after a few tries on a test server, seems to be a situation where the server is about to start building the transaction history but instead gets a notification from a peer that record number (some high number) is invalid and redirects it to repair it. The repair request is valid because the blank database won't have a record that far in it, but that redirects Timekoin to start working on the database near the end of the records instead of starting from the beginning and building up.
(0000016)
KnightMB   
2012-06-24 17:02   
(Last edited: 2012-06-24 17:02)
If you schedule a block check at say 3 for example, this will restart the process because it will start at the beginning of the transaction history and begin working it's way back up like before. It can still get interrupted by a peer request for invalid block check, so some further code will be needed to make it a little smarter.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
44 [Timekoin Server] Performance Issue minor always 2012-07-27 15:55 2012-07-27 15:55
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.7  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.7  
    Target Version: 1.7  
Summary: Qhash Verification is Now Required for all Timekoin Communications Protocols
Description: Version 1.5 and higher of Timekoin support Qhash verification and will now be required in v1.7 to help avoid peer conflicts with peers running older version (1.41 and lower).

Qhash is an extra field in a transaction queue to make sure that transactions in queue can be replicated from peer to peer without corruption along the way due to ISP deep packet modification or other forms of corruption along the way.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
43 [Timekoin Server] General Issue major random 2012-07-25 12:35 2012-07-25 12:37
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: high OS Version:  
Status: resolved Product Version: 1.6  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.7  
    Target Version: 1.7  
Summary: The Timekoin Treasurer program can become disabled and no longer process transactions
Description: The Timekoin Treasurer program module can become disabled and transactions start to pile up in the queue and never get processed.
Tags:
Steps To Reproduce: Very rare random chance of happening when there is a database error trying to poll the transaction history.
Additional Information:
Attached Files:
Notes
(0000036)
KnightMB   
2012-07-25 12:35   
Was able to reproduce in a test machine.
(0000037)
KnightMB   
2012-07-25 12:37   
An additional line of code was added to check for database errors before trying to process how many records exist in the transaction history. If a database error is present, the area that starts a new database will not run. This will also prevent the treasurer from being disabled.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
42 [Timekoin Server] New Feature minor N/A 2012-07-25 01:12 2012-07-25 01:12
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.7  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.7  
    Target Version: 1.7  
Summary: SSL Between Timekoin Peers with Port 443
Description: As the summary states, peers that are using SSL (HTTPS) instead of just regular (HTTP) can now have other peers connect to them via the SSL as peers will see the port 443 and switch to HTTPS connections instead of HTTP connections to that peer that reports it listening on port 443.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
41 [Timekoin Server] New Feature minor N/A 2012-07-25 00:52 2012-07-25 00:53
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.7  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.7  
    Target Version: 1.7  
Summary: First contact servers can now be modified from the Peerlist tab
Description: As the summary says, you can now change, delete, or add first contact servers in the peerlist tab of the timekoin GUI.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
38 [Timekoin Server] New Feature minor N/A 2012-07-07 14:20 2012-07-07 16:40
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.6  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.6  
    Target Version: 1.6  
Summary: Random polling of time from timekoin.net to check clock accuracy
Description: Timekoin servers will send random time polls to Timekoin.net to compare clock times for accuracy. If clock times are separated by more than 15 seconds, a warning will be displayed on the "Home" tab alerting the operator to the issue. Once the time variance is within the 15 second threshold, the warning will go away. This will not hinder any Timekoin server (in case Timekoin.net was having any issues) and the polling is randomized to happen every 2 to 30 minutes to keep network traffic down.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
39 [Timekoin Server] New Feature minor N/A 2012-07-07 14:29 2012-07-07 14:29
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.6  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.6  
    Target Version: 1.6  
Summary: Public messages can be encoded into any transaction from the GUI
Description: 64 character messages can be encoded into a transaction. Keep in mind that the message is visible to anyone willing to look inside the transaction data. So it's not recommended to put anything into the message (passwords, etc) that you don't want other people to read or examine.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
37 [Timekoin Server] New Feature minor N/A 2012-07-07 14:16 2012-07-07 14:17
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.6  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.6  
    Target Version: 1.6  
Summary: Better string building to increase performance of Timekoin
Description: Better string building and general optimizations across all of the Timekoin components increase the response time and speed by 50x for slower machines and near instant for all other modern Timekoin servers.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
36 [Timekoin Easy Key] New Feature minor have not tried 2012-07-07 14:13 2012-07-07 14:13
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.1  
    Target Version: 1.1  
Summary: Time polling added to service
Description: Time polling for peer time was added so that any Timekoin server can poll timekoin.net for the current unix time. This is avoid polling NTP servers around the world as it might cause an increase in traffic that is not welcome to the operators.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
35 [Timekoin Server] New Feature minor N/A 2012-07-03 15:30 2012-07-03 15:34
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.5  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.5  
    Target Version: 1.5  
Summary: Transaction Queue Manager per transaction verification ability in the queue
Description: Transactions are replicated around the Queue as fast as possible to gather up for the next processing cycle. If a transaction becomes damaged (missing data or wrong data) during transit, this can be replicated around the network causing the transaction to fail when it's finally processed by all the peers. All peers will now add a verification hash to the end of every transaction to allow peers to verify if the data received or sent has not been corrupted along the way.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
34 [Timekoin Server] New Feature minor have not tried 2012-07-01 14:41 2012-07-01 22:29
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.5  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.5  
    Target Version: 1.5  
Summary: Poll peer clocks for accuracy measurement
Description: Some servers have system clocks that are not in sync, causing out of sync generation issues or transaction issues. This new feature will allow the user to poll all active peers clocks to measure if their own clock is causing them issues staying in sync with the rest of the network.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000031)
KnightMB   
2012-07-01 22:29   
The "System" tab now has a button to "Check Relative Peer Times" to find out how in sync your Timekoin server is with the rest of the peers.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
33 [Timekoin Server] Feature Request minor have not tried 2012-07-01 13:58 2012-07-01 19:47
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.41  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.5  
    Target Version: 1.5  
Summary: Allow an option to disable or enable Local IP filtering
Description: Right now, Timekoin filters local IPs by default to avoid spreading them to other peers (since they won't work over the Internet anyway). For users running multiple server setups, the ability to turn off the feature would be useful as it would allow LAN peers to communicate and discover with each other.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000030)
KnightMB   
2012-07-01 19:47   
Radio option button added to "System" tab to enable or disable LAN based peers to through the peerlist.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
32 [Timekoin Server] New Feature minor N/A 2012-06-30 23:24 2012-06-30 23:25
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.41  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.5  
    Target Version: 1.5  
Summary: Transaction Queue Manager can now run multiple instances
Description: Transaction Queue Manager can now spawn more than 1 instance to gather up transactions to be processed. This can help large servers with a lot of connected peers as it takes time to cycle through all the peers to gather up data. Instead of polling one peer at a time, the system will now poll 1, 2 or 3 peers at once depending on the amount of transactions to be processed in the network queue.

This also helps to reduce network traffic for peer to peer history checking as the peer won't have to search for missing transactions if it missed them earlier in the queue due to high volume or traffic.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
31 [Timekoin Server] Feature Request minor have not tried 2012-06-30 02:13 2012-06-30 02:14
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.41  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.5  
    Target Version: 1.5  
Summary: Generation tab needs to show when the next peer election will take place
Description: I would be nice to know when the next peer election will happen.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000029)
KnightMB   
2012-06-30 02:14   
Next peer election information shows up in the "quick info" tip area by running future calculations for the next 200 cycles to see when the next peer election will take place.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
30 [Timekoin Server] Feature Request minor N/A 2012-06-29 19:45 2012-06-29 19:45
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.41  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.5  
    Target Version: 1.5  
Summary: Ability to assign permanent peers to the peerlist
Description: Feature request to assign permanent peers to the peer-list that never expire and can only be removed manually by the server administrator.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
29 [Timekoin Server] Operating System Issue major always 2012-06-28 13:20 2012-06-28 16:51
Reporter: KnightMB Platform: PC  
Assigned To: KnightMB OS: Microsoft Windows  
Priority: high OS Version: All  
Status: resolved Product Version: 1.4  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.41  
    Target Version: 1.41  
Summary: Windows running Timekoin isn't multi-tasking properly
Description: Windows does not let Timekoin multitask properly. Instead of being about to communicate with peers and process transactions at the same time, it is forced to do one thing at a time causing the other process to timeout waiting. This causes all kinds of weird things to happen such as loss of peer connections, generation issues, and general operation issues such as lagging behind the whole peer swarm constantly.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000028)
KnightMB   
2012-06-28 16:51   
Multitasking issue fixed for Windows systems.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
28 [Timekoin Server] Performance Issue minor random 2012-06-28 00:19 2012-06-28 00:59
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.4  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.5  
    Target Version: 1.5  
Summary: Transaction Foundation creation does not have enough time on slower systems
Description: Slower systems can not built a transaction foundation in the allocated 300 seconds if the block is rather large to hash.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000026)
KnightMB   
2012-06-28 00:20   
Our 1GHz Celeron test system can no longer build a transaction foundation in the 300 seconds allowed. Will look at longer times to allow completion for slower systems.
(0000027)
KnightMB   
2012-06-28 00:59   
Transaction foundation build time has been increased from 300 seconds max to 999 seconds max. Foundation is done more for index reasons to increase response time and won't interfere with the normal operations of Timekoin while running (even if it takes a long time to finish). Our test 1GHz Celeron was about to build the latest foundation in under 999 seconds, so any modern system will be able to complete the task much, much sooner.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
27 [Timekoin Server] Feature Request minor N/A 2012-06-27 18:19 2012-06-27 18:19
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.3  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.4  
    Target Version: 1.4  
Summary: Easy Key integration into Web based GUI for Timekoin
Description: The Send / Receive tab now has a field to translate Easy Keys to the full public key length when sending koins in a transaction.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
26 [Timekoin Server] Feature Request minor N/A 2012-06-27 16:11 2012-06-27 17:55
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.3  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.4  
    Target Version: 1.4  
Summary: Hash code for External Access by other programs or servers
Description: A hash code added to the "Options" tab so allow 3rd party software or servers to poll a Timekoin server to perform task such as look up the balance of a public key or other various task.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000025)
KnightMB   
2012-06-27 17:55   
Feature is now part of the "Options" tab.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
22 [Timekoin Server] Feature Request minor N/A 2012-06-26 00:18 2012-06-27 16:09
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.3  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.4  
    Target Version: 1.4  
Summary: Generation tab needs to show more technical details about the list
Description: Generation tab only shows how many peers have been elected and whether your own peer is in that list. More details would be useful such as what peers are being considered for the next election as well as what peers are already in the list.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000024)
KnightMB   
2012-06-27 16:09   
More technical details of what public keys are in the list as well as those waiting to be elected.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
24 [Timekoin Server] Feature Request minor N/A 2012-06-26 14:08 2012-06-27 14:20
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.3  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.4  
    Target Version: 1.4  
Summary: System logs need a search and filter ability
Description: Trying to read through a ton of logs is not fun, filters and search is needed.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000023)
KnightMB   
2012-06-27 14:20   
A filter ability was added, a search ability can be added for the future if the users really have a need for it or make enough request for it.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
25 [Timekoin Server] Feature Request minor N/A 2012-06-27 13:10 2012-06-27 13:39
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.3  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.4  
    Target Version: 1.4  
Summary: Area in GUI to tweak IP banning settings
Description: An area in the GUI needs to set to allow custom settings of the threshold to determine when an IP is flooding Timekoin and ban IP for 24 hours.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000022)
KnightMB   
2012-06-27 13:39   
New field in "System" tab added labeled "Max Peer Query" will allow customizing of the setting now.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
23 [Timekoin Server] Performance Issue minor always 2012-06-26 00:36 2012-06-27 02:39
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.3  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.4  
    Target Version: 1.4  
Summary: Timekoin does not close a connection after polling a peer for hash or transaction data
Description: Timekoin does not close the connection after making a connection to another peer to retrieve hash or transaction data. This can cause the build up of "open" connections at the peer end, which if the peer is busy enough, might overload a system with connection limits (like Windows) to where it is not accessible until the connections clear after 15 seconds.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000021)
KnightMB   
2012-06-27 02:39   
Each query or poll is set to request the connection to close as soon as the data is delivered instead of remaining open until the server timeout kicks in. Reducing the load on the the other peers across the network.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
21 [Timekoin Server] Performance Issue minor N/A 2012-06-25 00:35 2012-06-25 00:36
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.3  
    Target Version: 1.3  
Summary: Better memory management for longer uptimes
Description: Timekoin can terminate after a few days of continuous up-time due to a gradual climb of memory usage until it hits the server limit and shuts down requiring a restart to start again.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000020)
KnightMB   
2012-06-25 00:36   
The main & watchdog programs have memory clearing after every cycle now, appears to have stopped the gradual memory climb in test clients so far. Will mark fixed unless another issue is found.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
20 [Timekoin Server] Feature Request minor N/A 2012-06-25 00:32 2012-06-25 00:33
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: high OS Version:  
Status: resolved Product Version: 1.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.3  
    Target Version: 1.3  
Summary: Need backup tab for server keys
Description: Need a way to backup and restore server keys in case of server failure or wanting to move an account to a new server.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000019)
KnightMB   
2012-06-25 00:33   
New Backup tab added to web GUI, allows you copy keys to anything (text file, device, etc.) and also import new keys or overwrite existing keys.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
19 [Timekoin Server] General Issue major always 2012-06-24 16:56 2012-06-24 21:10
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: high OS Version:  
Status: resolved Product Version: 1.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.3  
    Target Version: 1.3  
Summary: PHP specific function only works with v5.3 or higher
Description: The 1.2 release is using gc_enable which only works in version php v5.3 or higher. Needs a check to not use this feature if the version is less than v5.3.
Tags:
Steps To Reproduce: Try to start Timekoin on a server with php version lower than v5.3
Additional Information:
Attached Files:
Notes
(0000017)
KnightMB   
2012-06-24 18:11   
A php version check is installed, anything less than version 5.3 and the gc_enable feature won't be activated.
(0000018)
KnightMB   
2012-06-24 21:09   
(Last edited: 2012-06-24 21:10)
This featured activation have been removed from v1.3 as these versions of PHP already have this feature enabled by default, so there is no benefit in turning it on again.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
16 [Timekoin Server] General Issue minor random 2012-06-23 22:41 2012-06-24 17:00
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.3  
    Target Version: 1.3  
Summary: Peers not aggressive enough to get elected to the generation pool
Description: When starting Timekoin for the first time, your peer must get elected before it can every start to generate. The peer doesn't seem aggressive enough to get elected, sometimes taking hours.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000011)
KnightMB   
2012-06-23 22:42   
I was able to reproduce this with a new peer. Seems it's not aggressive enough in submitting a request to a the network to be elected. Needs to be aggressive to get elected when other peers are also waiting in line to get elected.
(0000015)
KnightMB   
2012-06-24 17:00   
Generation management will submit a request every cycle to join the generation list instead of just when it detects it within it's own queue (as it might be in its queue, but not all the peers queue due to network congestion or other factors beyond its control).

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
18 [Timekoin Server] General Issue minor always 2012-06-24 14:37 2012-06-24 14:41
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.3  
    Target Version: 1.3  
Summary: Generation rate after 2 weeks inaccurate
Description: Generation rate after 2 weeks is incorrect, should be 3, not 2
Tags:
Steps To Reproduce: Generate currency for more than 2 weeks
Additional Information:
Attached Files:
Notes
(0000014)
KnightMB   
2012-06-24 14:41   
Rates are chart based rather than calculation as it is just as simple to code than trying to work out a math calculation that does the same thing. The math calculation was suppose to follow the chart rules, but instead it is easy just to code the chart rules in.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
15 [Timekoin Server] Performance Issue minor random 2012-06-23 15:07 2012-06-24 02:09
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.3  
    Target Version: 1.3  
Summary: Watchdog might release a program earlier than the timeout is normally set
Description: Watchdog keeps a watch on the other programs and if any becomes stuck, tries to reset it. Sometimes, watchdog can reset a program before it's finished, allow another instance to start causing two to run at the same time. For example, the Transaction Clerk might get started twice, doubling the load to the database and other peers requesting information.
Tags:
Steps To Reproduce: Random, varies from system to system.
Additional Information:
Attached Files:
Notes
(0000013)
KnightMB   
2012-06-24 02:09   
A 15 second grace period was added so that the rare problem of a script being stuck (but not being shutdown after the timeout) right after the watchdog has already detected and tried to reset the script to prevent a second instance from spawning at the same time while the other has not stopped yet.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
13 [Timekoin Server] General Issue minor random 2012-06-22 18:29 2012-06-22 18:44
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.2  
    Target Version: 1.2  
Summary: Private IP ranges need to be filtered by Peerlist
Description: Private IP address don't work across the Internet, so it's a waste of resources to include them in the list or try to contact them across the Internet since it will always fail.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
12 [Timekoin Server] Feature Request minor N/A 2012-06-22 18:27 2012-06-22 18:43
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.2  
    Target Version: 1.2  
Summary: Add a button to show reserve peers and a button to manually add peers to the Peerlist tab
Description: Reserve peers are hidden, can't see what they are.

Need the ability to manually add peers for those that have an Internal network of Timekoin servers that they don't want to expose to the Internet (usually when doing a relay-chain setup)
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
10 [Timekoin Server] Performance Issue major random 2012-06-22 16:37 2012-06-22 18:15
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: high OS Version:  
Status: resolved Product Version: 1.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.2  
    Target Version: 1.2  
Summary: Generation Peerlist has trouble getting in sync with the rest of the network
Description: The generation peerlist should update from a blank list within a minute or two, but instead can take a long time to get all the generating peers. The long wait causes is to trigger a stale list purge, thus make it cycle over and over trying to build it's generating peer list.
Tags:
Steps To Reproduce: Clear generation list, let it rebuild from other peers, process takes too long.
Additional Information: It only puts 1 peer in the list at a time, even though the peers are coded to answer with over 50 peers at a time from their own list.
Attached Files:
Notes
(0000010)
KnightMB   
2012-06-22 18:15   
When going through the list of generating peers, only one was being added from the list. So it takes too long to add peers this way before the list becomes stale.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
11 [Timekoin Server] Performance Issue minor random 2012-06-22 16:52 2012-06-22 16:54
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.2  
    Target Version: 1.2  
Summary: Peer IPs can get auto-banned by accident when traffic is busy
Description: Your peers can get banned by accident if they are busy working with your peer.
Tags:
Steps To Reproduce: Get two busy peers to communicate with each other.
Additional Information: By default, each peer tries to limit the other peers to less than 100 queries per cycle (usually 10 seconds). The limit can be reached by accident when a peer is busy talking to another peer.
Attached Files:
Notes
(0000009)
KnightMB   
2012-06-22 16:54   
The query count protects servers from being attacked either by accident or on purpose.

Max queries was doubled to 200. 100 Seems to be a good number for most servers, but a future feature to allow the user to change this would be a better solution.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9 [Timekoin Server] Performance Issue minor random 2012-06-22 04:42 2012-06-22 16:34
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.2  
    Target Version: 1.2  
Summary: Peerlist can get duplicates
Description: The peerlist can get duplicates in the connection list, doesn't seem to be filtering same peer address (domain and/or IP)
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
6 [Timekoin Server] Feature Request tweak N/A 2012-06-21 13:49 2012-06-22 16:34
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: low OS Version:  
Status: resolved Product Version: 1.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.2  
    Target Version: 1.2  
Summary: Add uptime, current transaction block, current foundation block to system information tab
Description: A few request to add this info to the system tab for reference.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8 [Timekoin Server] Performance Issue minor always 2012-06-21 23:21 2012-06-22 16:33
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.2  
    Target Version: 1.2  
Summary: Bogus or duplicate transaction not filtered from the queue
Description: The transaction queue can fill up with bogus or duplicate transactions. The transactions are never recorded as they are eventually purged, but it still waste processing time to do it.
Tags:
Steps To Reproduce: Happens when another peer isn't purging it's queue properly and has stale transactions that get replicated across the network every cycle.
Additional Information:
Attached Files:
Notes
(0000008)
KnightMB   
2012-06-21 23:24   
The queue manager normally just checks for a valid transaction by testing out the keys and hashes. But the timestamp is usually ignored, thus old transactions can land in the queue even though they will be purged when it comes time to enter them in the transaction history due to being duplicates. The additional server overhead can be saved if the stale transactions are filtered from ever entering the system to begin with.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
5 [Timekoin Server] Performance Issue major always 2012-06-21 02:51 2012-06-22 16:32
Reporter: KnightMB Platform: PC  
Assigned To: KnightMB OS: Windows  
Priority: normal OS Version: XP, Vista, or 7  
Status: resolved Product Version: 1.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.2  
    Target Version: 1.2  
Summary: The part of Timekoin that checks to make sure the database is active has a memory leak
Description: The main.php script of Timekoin does a routine check to make sure the database is active and if inactive, tries to re-establish a connection. After so many failures, it gives up and exits to avoid any further issues until the user attempts a restart of Timekoin. This check appears to cause a memory leak in Windows where if you check the task manager, you'll notice a php.exe process eating up more ram as time goes forward.
Tags:
Steps To Reproduce: Setup Timekoin on Windows (any version) and just let Timekoin run for a few days. Check the task manager from time to time.
Additional Information:
Attached Files:
Notes
(0000007)
KnightMB   
2012-06-21 02:57   
Currently testing a suggested fix of simply using a "failed" query as a sign of database failure and then attempt to reconnect database. After 5 failures (spaced about 10 seconds apart on each retry), the program will exit to avoid further complications.

As a side note, the mysql_ping being used to check for "active" database actually causes a 5 second delay in Windows (not seen on Linux or Mac). So future versions will simply just not use the command anymore as even the PHP.net website recommends against using this anymore.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7 [Timekoin Server] General Issue minor always 2012-06-21 16:29 2012-06-21 17:14
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.2  
    Target Version: 1.2  
Summary: Last Generation time is off by 5 minutes
Description: If you compare when currency is actually generated and what the timer says, it's always off by 5 minutes.
Tags:
Steps To Reproduce:
Additional Information: GUI related bug, does not affect actual currency generation.
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2 [Timekoin Server] General Issue minor always 2012-06-19 14:54 2012-06-20 16:23
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.0  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.1  
    Target Version: 2.41  
Summary: Server Balance can be incorrect shortly after a Transaction Foundation is created
Description: Server balance is lower than it should be within 5 hours of a transaction foundation creation event.
Tags:
Steps To Reproduce: Just wait until another transaction foundation is created, check the balance in the web GUI. It will report lower than it should until the 5 hours has passed.
Additional Information: Transaction Foundations are created by all peers every few days as a way to index the Transaction History for quick access to balances. As a way to increase performance, the Timekoin server builds a balance index of recently checked public keys. This helps the server avoid running a balance check on the entire transaction history every time a transaction is being processed.

To avoid confusion in the GUI, the balance index is rebuilt shortly after transaction foundation creation process. During that in-between time, the balance index is still "stale" as it only has the balance of the keys in the index from a previous few days. This ends up reporting a "lower" total than it should in the GUI.

This has no affect on the transaction history; all transaction are still there and no balance hacks or double-spending could take place. It's merely confusing to the server administration should he/she be looking at the balance screen during that time.
Attached Files:
Notes
(0000001)
KnightMB   
2012-06-19 15:01   
This has been fixed for the next release.

The problem lay in the function that checked public key balances. It did not account for the time "lapse" during it's check and thus a gap of time means anything created (transactions or generation) were not being counted. This is what caused the lower than normal balance to show up in the web GUI.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4 [Timekoin Server] General Issue major random 2012-06-19 21:33 2012-06-20 16:23
Reporter: KnightMB Platform:  
Assigned To: KnightMB OS:  
Priority: high OS Version:  
Status: resolved Product Version: 1.0  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.1  
    Target Version: 1.1  
Summary: Malformed Attributes in Transactions can stall a Block check or repair
Description: If a new (or shutdown) Timekoin server is coming online and needs to catch up with the network peers, a malformed attribute is not filtered properly. This causes Timekoin to hang with an error message that there is "too much peer conflict" many times in the logs (more than normal)
Tags:
Steps To Reproduce: Any server that is trying to sync up with it's peers that either gets a corrupt response or a malformed response on purpose, becomes stored in the database as "H-" or "G-" for example instead of "H" or "G".
Additional Information: This relates to the transaction clerk module that is responsible for keeping transaction records up to date.
Attached Files:
Notes
(0000003)
KnightMB   
2012-06-19 22:39   
(Last edited: 2012-06-19 22:41)
A missing "?" in the string check was letting more than a single character bleed through. So instead of an Attribute being tagged as "T" transaction for example, it would be tagged as "T-" which when it works it way through transaction verification process fails because Timekoin thinks this is a bogus transaction ( T != T- basically) and should be ignored/deleted.

The next version will also apply a fix to the database to remove any corrupt attributes the next time Timekoin is started. This will insure that even after the new fix is applied, old, malformed attributes don't remain in the database.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
3 [Timekoin Server] General Issue minor always 2012-06-19 17:36 2012-06-20 16:23
Reporter: epstrom Platform:  
Assigned To: KnightMB OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.0  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 1.2  
    Target Version: 2.41  
Summary: Unable to jump to row 0 on MySQL result
Description: Warning: mysql_result() [function.mysql-result]: Unable to jump to row 0 on MySQL result index 26 in /home/directsp/public_html/epstrom.com/timekoin/function.php on line 685

Warning: mysql_result() [function.mysql-result]: Unable to jump to row 0 on MySQL result index 27 in /home/directsp/public_html/epstrom.com/timekoin/function.php on line 686
Tags:
Steps To Reproduce: Open Home , Send / Receive Pages
Additional Information:
Attached Files:
Notes
(0000002)
KnightMB   
2012-06-19 21:45   
This is the result of the "mysql_result" not finding the data requested. It's actually not an error (because if there is no row, then it reports 0). But for some reason is logged by PHP due to a E_WARNING setting for error reporting. We noticed during development long ago and the only to get rid of it is to turn off the E_WARNING by removing it from "error_reporting" in your php.ini file.

The only solution would be to use a slower way to getting the same information with more commands. Our hope is that this bug in PHP will one day be fixed.
(0000004)
epstrom   
2012-06-20 06:31   
error_reporting(NULL);

could be used at configuration.php, since it's used by every page
(0000005)
KnightMB   
2012-06-20 16:05   
Thanks for that jewel, all these years I thought this could only be disabled in the php.ini file, but a php command that does it for you is even better. This will certainly be included in the next release!
(0000006)
KnightMB   
2012-06-20 16:23   
error_reporting(E_ERROR | E_CORE_ERROR | E_COMPILE_ERROR);

This was added to the code to show only fatal errors in the software, should they happen. All warnings that have no effect on the software will no longer be logged or displayed.