aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* embed user passwds to the code structs.alpaylan2021-04-144-20/+55
|
* add user passwds.alpaylan2021-04-140-0/+0
|
* Simplify the block validation processYigit Sever2021-04-141-19/+16
| | | | 2 TODOs down!
* Fix post transaction testYigit Sever2021-04-141-1/+1
|
* update todoalpaylan2021-04-141-1/+2
|
* fix the serde if tests.alpaylan2021-04-141-7/+19
|
* delete unnecessary imports.alpaylan2021-04-141-2/+1
|
* finished auth request testing.alpaylan2021-04-141-1/+24
|
* finished metu id testing.alpaylan2021-04-141-0/+14
|
* finished user testing.alpaylan2021-04-142-3/+33
|
* finished naked block testing.alpaylan2021-04-142-7/+38
|
* finished block testingalpaylan2021-04-142-1/+35
|
* finished claim testing.alpaylan2021-04-141-0/+35
|
* finished claim testing.alpaylan2021-04-141-1/+8
|
* start testing schemaalpaylan2021-04-142-2/+22
|
* test functions are generated.alpaylan2021-04-141-0/+97
|
* update todoalpaylan2021-04-141-1/+1
|
* update todoalpaylan2021-04-141-1/+4
|
* remove unused part.alpaylan2021-04-141-12/+1
|
* add balance check to transactions.alpaylan2021-04-141-0/+35
|
* Add empty block testYigit Sever2021-04-143-5/+9
|
* Add new testYigit Sever2021-04-141-0/+27
|
* Revise testsYigit Sever2021-04-141-87/+62
|
* Implement multithreading for example minerYigit Sever2021-04-141-15/+48
|
* Update TODOYigit Sever2021-04-131-4/+9
|
* Add verbose error messagesYigit Sever2021-04-135-61/+182
| | | | | | | | | Not happy with the solution one bit but using error.rs at https://blog.logrocket.com/create-an-async-crud-web-service-in-rust-with-warp/ was not working Basically we just handcraft every single response on the spot, there is some repetition and it's ugly but need to move on
* Fix docs againYigit Sever2021-04-131-2/+2
|
* Fix docsYigit Sever2021-04-131-1/+1
|
* Refactor authorized propose functionsYigit Sever2021-04-132-127/+192
| | | | | | | | | | | | | | They were getting spaghetti so; new function: handlers::authorize_proposer(), handles the jwt stuff, NOT async and _may_ cause trouble down the road but then again the stuff it does used to be (repeated) in the functions so how bad can it be If else chains were getting unwieldy; https://refactoring.com/catalog/replaceNestedConditionalWithGuardClauses.html so now everything is returning early, might make verbose error handling easier
* Fix typoyigit sever2021-04-131-1/+1
|
* Update 'TODO.md'yigit sever2021-04-131-0/+1
|
* Require authorization for Block POSTYigit Sever2021-04-135-57/+101
| | | | | Not tested because it's impossible to follow without verbose error messages, failing 1 test
* Tracking logo and faviconsYigit Sever2021-04-137-0/+0
|
* HousekeepingYigit Sever2021-04-137-480/+528
| | | | | | Moved tests out of routes.rs into their own file Learned how to use lib.rs, now we have cargo doc support as well
* Update todo and readmeYigit Sever2021-04-132-14/+12
|
* implement user authentication using jwtalpaylan2021-04-128-32/+374
|
* six rightmost zeros for miningalpaylan2021-04-122-4/+4
|
* Add new TODO itemsYigit Sever2021-04-121-0/+5
|
* Implement proof-of-workYigit Sever2021-04-1210-38/+207
| | | | | | | | Using blacke2s: https://docs.rs/blake2/0.9.1/blake2/ Using this guy's hash checker https://gist.github.com/gkbrk/2e4835e3a17b3fb6e1e7 blacke2s with 5 bits 0 can mine a block between 20 seconds to 359 during my tests, hope it'll be fun
* Ignore blocks and users dirsYigit Sever2021-04-121-0/+2
|
* Update brag sectionYigit Sever2021-04-121-2/+1
|
* Merge remote-tracking branch 'origin/main'Yigit Sever2021-04-121-0/+10
|\
| * Add TODO itemsyigit sever2021-04-111-0/+10
| | | | | | | | Tests and verbose error messages
* | Implement User handling and authenticationYigit Sever2021-04-127-41/+237
|/ | | | | | | | | | | | | | | | | | | | | | | | New struct: User, corresponds to a student Blocks and users are persistent (written to a text file) PostgreSQL would've been overkill, we have 30 students AuthRequest is the representation for incoming register requests and User is the inner representation Students who are enrolled to the class are hardcoded, only they can register new accounts There are two new tests, one checks if a priviliged (=enrolled) user can create an account and the other checks if a unpriviliged one cannot There are quick verbose error messages that I'm not married to, might move on to something better honestly There's nothing stopping a malicious user to pre-register everyone with mock public keys and effectively lock everyone out, what's a good secret we can use?
* Rephrase README to update design decisionsYigit Sever2021-04-111-13/+21
|
* Add auth scheme JWTYigit Sever2021-04-092-2/+8
|
* Remove unused code and clean up commentsYigit Sever2021-04-091-197/+18
|
* Remove unused code from filtersYigit Sever2021-04-091-5/+0
|
* Add HTTP/1.1 resources to READMEYigit Sever2021-04-091-0/+4
|
* Add test TODO items to routesYigit Sever2021-04-091-0/+4
|