inkonchain / inkonchain/node

what even is this? hours of nothing.

Open
#63 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
36.5k
Forks
643
PR merge metrics
No merged PRs in 30d

Description

What does it MEAN?

root@InkSpecial:~# docker logs --tail 10 ce1451fe5d68 -f
INFO [05-13|09:24:02.893] HTTP server started                      endpoint=[::]:8551 auth=true  prefix= cors=localhost vhosts=*
INFO [05-13|09:24:12.934] Loaded local transaction journal         transactions=133,425 dropped=0
INFO [05-13|10:24:27.499] Regenerated local transaction journal    transactions=124,766 accounts=298
INFO [05-13|11:24:28.033] Regenerated local transaction journal    transactions=124,766 accounts=298
INFO [05-13|12:24:28.600] Regenerated local transaction journal    transactions=124,766 accounts=298
INFO [05-13|13:24:29.161] Regenerated local transaction journal    transactions=124,766 accounts=298
INFO [05-13|14:24:29.706] Regenerated local transaction journal    transactions=124,766 accounts=298
INFO [05-13|15:24:30.266] Regenerated local transaction journal    transactions=124,766 accounts=298
INFO [05-13|16:24:30.808] Regenerated local transaction journal    transactions=124,766 accounts=298
INFO [05-13|17:24:31.352] Regenerated local transaction journal    transactions=124,766 accounts=298

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Docker command and the repeated Regenerated local transaction journal entries in the issue body. Determine what the journal regeneration indicates and whether the repeated hourly messages represent expected Ink Node behavior; the issue does not define a concrete change or a testable done state.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
devops, infrastructure
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.