Skip to content
This repository has been archived by the owner on Apr 16, 2019. It is now read-only.

Steem integration #121

Closed
wants to merge 5 commits into from
Closed

Steem integration #121

wants to merge 5 commits into from

Conversation

xeroc
Copy link

@xeroc xeroc commented Oct 16, 2016

Basic Steem integration to support:

  • Obtain (and show) STEEM public key given a HDnode(path)
  • Sign a transfer operation given all the required parameters (show details and wait for confirmation on the trezor)

Only relevant changes are in:

  • Makefile
  • steem.h and steem.c
  • fsm.h and fsm.c
  • messages.c and messages.options

The submodules require an merged/updated trezor-crypto (already merged into the official release) and trezor-common (pull request pending)

@xeroc
Copy link
Author

xeroc commented Oct 19, 2016

Properly use HD node with 'pubkey_n' to obtain a key from the HD hierarchy

@xeroc
Copy link
Author

xeroc commented Nov 25, 2016

What needs to be done to get this pull request merged eventually? I had to fix merge conflicts twice already and don't know if it makes sense to fix them again if I don't know that the PR will be merged

@prusnak
Copy link
Member

prusnak commented Nov 25, 2016

Hey Fabian! No need for the rebase, I'll do it. I returned back to merging T1 features recently and this is on my list. Sorry for not merging this earlier :-(

Can you please sumarize the state of integration efforts from Steem side? i.e. what software and/or services already integrated TREZOR and what software/services are waiting for it?

@xeroc
Copy link
Author

xeroc commented Nov 28, 2016

Can you please sumarize the state of integration efforts from Steem side? i.e. what software and/or services already integrated TREZOR and what software/services are waiting for it?

The current firmware supports account_updates and transfers for STEEM, so the very basic feature of a secure MVP.
We also plan to integrate it into piston which is a python client for Steem.

The firmware is almost ready and I plan to add more tests to the actual firmware using python-trezor in the weeks ahead.

Our biggest problem is that we don't yet know how to fund further development of steem-trezor. There are many opportunities and features that can and should still be added to Trezor. If we manage to secure some funding, we would like to put more work and time into this. We have already tried to reach out to Alena to begin discussions of a joint venture of some kind but haven't heard back yet. I would request to continue the funding discussion off-github. You can reach me at mail@xeroc.org

@prusnak
Copy link
Member

prusnak commented Apr 15, 2019

We are moving to monorepo: https://github.com/trezor/trezor-firmware

@prusnak prusnak closed this Apr 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants