[Passed] Motion to join FLOT - dysconnect

[Dhume]

I am still interested in joining the FLOT team. What is holding me back is that I’m still not quite sure as to the technical challenges being part of FLOT will produce. Maybe it’s an idea to have a test run week so to speak, so everyone who is voted to be a member of FLOT can have a few runs at signing and producing multi sig transactions.

Also similar to @masterOfDisaster is it possible to sign transactions without having to be near the same computer all the time? Aka can we find a method to sign multi sig from ones phone for example. Doing a practice run with some small amounts of funds would also allow us to experiment with ways to communicate between ourselves. I imagine for most actions a dedicated forum post would suffice but in case of emergency’s we might want additional means of communicating that are faster?

[mhps]

I was also thinking it would be better if there is a period when every community member is welcome to try out in a sand box and contribute to how best to do it. Then those who feel up to the task can be elected to the group.

[Nagalim]

Maybe we should do this on testnet?

[dysconnect]

I’m building some scripts that use github to track spendable inputs and broadcast signed transactions. Porting to a mobile device requires either a separate channel or a git library on android.

For now you should assume that the response times aren’t so strict until a viable tool comes out - you just need to tell shareholders you will sign transactions when you get home etc. See if you are comfortable with the most basic multisig work flow.

By the way, I want to know whether blockexplorer.nu has an API to retrieve transactions to an address…

[mhps]

Often all I have access to is a web browser. As a framework question, can signing be done over the web? even if a private web server is needed to be set up? (over a vps or raspberry pi maybe)

[dysconnect]

Yes, also better and easier if your server has access to nud. You can do anything if you have a web server. Just remember for signing capabilities 1) you need to be able to create transactions (from inputs etc.) 2) you need to broadcast the signed transaction 3) you need to fetch partially signed transactions from the broadcasting channels used by other signers. Then somebody has to send out the transaction through nud.

[mhps]

For the R-pi there is no problem running nud.

[dysconnect]

It can be something like this:

1. Use authentication and SSL

2. Accepts HTTPS requests that do the following, passing args to nud if necessary:

• Create raw transaction just given amount, multisig address, recipient
• Sign raw transaction (password decrypt wallet if necessary)
• Verify raw transaction and signatures
• Broadcast raw transaction on network

3. These should be tracked on your R-pi

• Unspent outputs of the multisig address (tracked using nud or fetched from others)
• Raw transactions pending signatures, and which people signed

[Cybnate]

Added your motion to the datafeed as you took the initiative and the draft have been up for a while.
Straightforward and clear motion, will work my way through the other motions in the next few days.

[ttutdxh]

I am ready to help with that, do you have a public github repository?

[dysconnect]

dc-tcs

Basically the same account I used for the meeting. There’s a dysconnect on github but I’m pretty sure that’s not me (not 100% sure it wasn’t an account I created then abandoned at some point). dc-tcs/git-multisig contains the script where dc-tcs/flot-operations is a repository for storing information needed for multisig.

So far the code is messy and horribly undocumented, but luckily it’s still short. Basically the only thing I can claim to have implemented is the tracking of unspent outputs given an address (currently the recent 100k grant address of JL for tier 4) and forming a transaction, syncing the repository with the blockchain if nud is available. It’s a long way from being usable but there’s stuff being done.

[crypto_coiner]

voted –

[tomjoad]

@assistant motion vote cb23c76e21e6ef7a568161e817869168f5273c4f

[assistant]

Hi @tomjoad

Here are the details for the Motion Vote on cb23c76e21e6ef7a568161e817869168f5273c4f:

---

##cb23c76e21e6ef7a568161e817869168f5273c4f
Blocks: 5001 (50.010000%)
Share Days: 1377545936 (37.517576%)

---

[tomjoad]

This motion has passed. Congratulations @dysconnect, we look forward to seeing your ideas on FLOT.

[jooize]

Was the role of share days removed?

Edit: Or did it never play a role? I might be mixing it up with the errorneous count of that motion a while back.

[dysconnect]

I think we’re still using SDD. Should be another day until SDD crosses 50%.

[dysconnect]

The motion has passed. Thanks to everyone who’s voted.

Given the current state I’ll focus on the technical aspects at least until we take over NBT signing from FSRT. I’ll also make sure my scripts are in a workable state before I spend time catching up with regulatory issues that are left out of Jordan’s motion.

[jooize]

I believe 90 days has passed since the passing of this motion, and it’s time to pay @dysconnect 435 US-NBT unless shareholders are dissatisfied with their service.

According to the motion, I also understand it as because @dysconnect has not been paid by the end of a cycle, they have the right to withdraw from FLOT.

• Where does @dysconnect want the 435 US-NBT sent for payment of the first cycle?
• Am I correct in assuming FLOT will send them to @dysconnect?
• Will @dysconnect continue to be part of FLOT?

[dysconnect]

Thank you for bringing this up. I figured a custodian grant but getting FLOT to send money is easier, or there will be 8 custodian grants to keep track of.

A more proper way would be to get shareholders to vote on a single motion on payment methods and then take funds out of sell side.

In lieu of a motion perhaps we can ask whether a shareholder would disapprove of such an arrangement.

Either way I’ll keep working in FLOT for up to 2 weeks before I receive funds. Next time I’ll bring it up myself 2 weeks before the 90-day limit (didn’t keep track of the dates this time).