Great work... is the bitshares js lib a port of bitcore as a base? Can you sign transactions? You still need a node to run to make RPC calls right? Is the mail system the foundations of "talking" to the library and thus make RPC calls to the bitshares node?
I'm just curious as to what you see the big picture here as where the bitshares JS is going together with the mail project.
I'm guessing web wallets and market place apps would use the JS library for efficiency purposes over talking directly a bitshares node?
well said: yes to all ..
I'm only using a small part of bitcore. I do like that project a lot, it is a valuable resource. It is quite large but they are planning to modularize it. Also I can trim out what we need if it comes to that.
BM can correct me if I get something wrong! Basically, the efficiency comes from using the mailbox mainly because you know what belongs to you (it is in your mailbox). You don't know who sent it or what it is unless you can derive the private key
to decrypt it ( this requires your private key ). So the mail is reasonably private. I'm assuming we utilize default mail servers initially but the flexibility to re-configure and add redundancy is already built-in should someone have a need. I imagine this will be the primary means of transferring transactions and will become a selling point for delegates that run a separate mail server. Here is Nathan's paper BitShares Mail