Bitgrin XBG
$0.00032 0.00%
Bitgrin 的创新性在于结合了比特币分配参数和MimbleWimble隐私协议
Communication in Bitgrin’s Discord
XBG社区志愿者

Yesterday, the developer of Bitgrin communicate with mumbers of Bitgrin community. Some details and principles of Bitgrin-Pay and non-transaction are listed on discord of Bitgrin.


昨天,Bitgrin的开发人员和社区成员在discord上讨论了关于BitgrinPay和非交互交易的细节。

Bladedoyle是grin的开发者在grin上贡献了1600多行代码。


Q&A 1:


bladedoyle(Pool Admin)


Bitgrin-Pay is a specification for an API allowing a client (wallet) to request and submit transaction slates. It is similar to the KingFish wallets ability to request a payment from the pool. The server-side implementation is up to the exchange/pool so there isnt really any source code to publish, just the specification.  Though I guess there could be a "reference implementation".

Bitgrin-Pay is not suitable for user-to-user transactions since it still requires one side to have a network port open and a request service running.


Bitgrin-Pay是允许客户端(钱包)请求和提交交易记录的API范式。这类似于KingFish钱包从池中付款的功能。服务器端实现取决于交易所/池,因此实际上没有要发布的任何源代码,只有规范。 虽然我猜可能会有一个“参考实施”。

Bitgrin-Pay不适合用户到用户的事务,因为它仍然需要一侧打开网络端口并运行请求服务。


nuka


so it could be possible to receive XBG from exchanges without port forwarding if the exchange has enabled this function and the kingfish wallet has also implemented the function to receive from the exchange same like we can receive xbg from mining pool?


因此,如果交易所启用了此功能,并且翠鸟钱包还实现了从交易所接收的功能,就像可以从采矿池接收xbg一样,那么有可能在没有端口转发的情况下从交易所接收XBG?


bladedoyle(Pool Admin)


Yes, exactly


是的


Q&A 2:


MrJimmy


can it be that it can be used for wallet to wallet in the future? Because I readed this in a other chat:

将来可以用于钱包吗?因为我在其他聊天中阅读了此内容:



nuka


that means bitgrinpay is completely different from grinbox and Hedwig?

这意味着bitgrinpay与grinbox和Hedwig完全不同吗?


bladedoyle(Pool Admin)


@MrJimmy It may be that "BitGrinPay" is being used as a more generic term which includes several different protocols. But only a payment request API is described in the github bitgrin/BitGrinPay document. I am guessing the chat above is referring to "Non-Interactive Transactions" mentioned in https://bitgrin.substack.com/p/a-glimpse-into-q4-adopt

@nuka The payment request API specification is completely different from grinbox and Hedwig. My (limited) understanding of the "Non-Interactive Transactions" is that payments will be relayed through bitgrin nodes, which, yes, is different from grinbox and Hedwig.

@MrJimmy可能是“ BitGrinPay”被用作更通用的术语,其中包括几种不同的协议。但是github bitgrin/BitGrinPay文档中仅描述了付款请求API。我猜上面的聊天是指https://bitgrin.substack.com/p/a-glimpse-into-q4-adopt中提到的“非交互式交易”

@nuka付款请求API范式与grinbox和Hedwig完全不同。 我对“非交互式交易”的理解(有限)是,付款将通过bitgrin节点进行中继,是的,这与grinbox和Hedwig不同。


Q&A 3:


pharazen


To be clear, the api specification is one component of BitGrinPay. We use it as an umbrella term for a variety of methods to make payments easier.

What we’re planning to release next month is the sidecar on full nodes that transmits encrypted slates without a central server.

Grinbox is just someone’s Amazon web server instance. Quite different

需要明确的是,api范式是BitGrinPay的组件之一。 我们将其用作各种方法的总称,以简化付款方式。

我们计划在下个月发布的是完整节点上的Sidecar,该节点无需中央服务器即可传输加密的文件。

Grinbox只是某人的Amazon网络服务器实例。 很不一样


Bgmeeyer


这与beam当前系统的工作方式相似吗?

据我了解,他们将tx平板存储在其p2p网络中的节点中


pharazen


I don’t concern myself too much with Beam.

But “store tx data in P2P nodes” is very similar to every P2P payment system ever created

我对Beam并不太担心。

但是“将Tx数据存储在P2P节点中”非常类似于曾经创建的每个P2P支付系统


Bgmeeyer


Isn't the implication of that design though that txs are still interactive, i.e both parties have to partake in the process of creating the tx and are using nodes in the network to act as message caches for the protocol

尽管tx仍是交互式的,但这不是设计的含义,即,双方都必须参与创建tx的过程,并使用网络中的节点充当协议的消息缓存


pharazen


By itself yes, but we are adding support for non-interactive transactions

就其本身而言,但是我们正在增加对非交互式事务的支持


Bgmeeyer


Ok awesome

Is there any info available current about what protocol/strategy you will employ to achieve non interactivity? I have read that it is possible to do it and that I think beam is, but at the expense of leaking more information about the contents of the transaction to the network.

还行吧

目前是否有任何信息可用于实现非交互性的协议/策略? 我已经读过,有可能这样做,而且我认为Beam是可行的,但是以将有关交易内容的更多信息泄漏到网络为代价。


pharazen


We have two strategies, the first being using primed outputs from receiver, which we know works. The second is to use BLS scheme, which it’s still something we’re researching and not sure if we’ll go with

Are you a developer?

We could use more help with development

我们有两种策略,第一种是使用接收器准备好的输出,我们知道这是可行的。第二种是使用BLS方案,这仍然是我们正在研究的问题,不确定是否会继续使用

您是开发人员吗?


Bgmeeyer


I appreciate these details thanks :) I am very inexperienced with rust unfortunately and am not a cryptographer, but I am very interested in all the protocols and cryptography behind mw.

Just not a professional or anything

我非常感谢这些细节:)不幸的是,我对rust非常缺乏经验,并且不是密码学家,但是我对mw背后的所有协议和密码学都非常感兴趣。

只是不是专业人士


pharazen


I see. Well, if you see anyone else using some other approach feel free to share it with me. From my research there are no MW projects other than our own doing anything that useful, it’s all shine and gloss, very little substance.

I spent time early on researching Beam and ended up just feeling foolish to have wasted my time. Their technology is built to be easy to use, but privacy is not a priority and they will make every last concession to privacy in favor of usability

我懂了

好吧,如果您看到其他人使用其他方法,请随时与我分享。根据我的研究,除了我们自己做的所有有用的事情之外,没有其他MW项目,它们都是表面化的,几乎没有实质性内容。

我花了一些时间在研究Beam上,结果浪费了我的时间而感到愚蠢。 他们的技术易于使用,但是隐私不是优先考虑的问题,他们将尽一切可能的隐私权让利于可用性


Bgmeeyer


Interesting, I appreciate your perspective on this as I am still familiarizing myself with all of the details of the mw protocol and so have not evaluated beams decisions technically yet for myself. :)

Is there anywhere where I can read about primed receiver outputs in more detail btw

有趣的是,我很欣赏您对此的看法,因为我仍在熟悉mw协议的所有细节,因此尚未为我自己从技术上评估波束决策。 :)

有什么地方我可以更详细地了解预备接收器的输出


pharazen


That’s just basics of the transaction model

这只是交易模型的基础

2019年12月17日 16:12图文分享