Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jun 17 23:30
    GeneFerneau synchronize #3643
  • Jun 16 21:02
    GeneFerneau synchronize #3643
  • Jun 11 20:01
    GeneFerneau synchronize #3645
  • Jun 11 19:51
    GeneFerneau commented #3645
  • Jun 11 19:30
    DavidBurkett commented #3645
  • Jun 11 19:21
    GeneFerneau commented #3645
  • Jun 11 19:10
    DavidBurkett commented #3645
  • Jun 11 18:59
    GeneFerneau commented #3645
  • Jun 11 14:41
    deevope closed #3525
  • Jun 11 14:24
    DavidBurkett commented #3645
  • Jun 10 19:49
    GeneFerneau commented #3645
  • Jun 10 15:45
    quentinlesceller commented #3645
  • Jun 10 13:42
    quentinlesceller commented #3644
  • Jun 10 13:42

    quentinlesceller on master

    Fix ROARING_ARCH environment va… (compare)

  • Jun 10 13:42
    quentinlesceller closed #3644
  • Jun 10 13:42
    quentinlesceller closed #3641
  • Jun 08 21:45
    GeneFerneau synchronize #3643
  • Jun 08 00:14
    xiaojay closed #3637
  • Jun 08 00:14
    xiaojay commented #3637
  • Jun 07 16:27
    phyro commented #3637
Grin Talk
@newtownf1
The topic of the show was ASICS and Moneros resistance . So to be fair to them , they didn’t even need to mention grin when I asked them their thoughts on grin because the show is called “monero talk”
John Tromp
@tromp
in the past, Monero has toyed with the idea of adopting Cuckoo Cycle as PoW
and grin's dual pow approach is occasionally brought up in Monero PoW discussions
Grin Talk
@newtownf1
Thanks for your input tromp
umma08
@umma08

harmony mining is discussed in Monero POW talks, but the loose consensus is that is not verified or empirically tested as offering a verifiable benefit/risk vector ratio.

iirc a lot of the arguments against harmony mining were raised originally by ZCash.

Grin Talk
@newtownf1
@umma08 hello @umma08
umma08
@umma08
hey newtonf1
energyburn
@energyburn
Anyone know if there has been any talk of developing ECDSA based multisig, instead of HTLC based multisig into one of the wallets?
viteshan
@viteshan
Anyone know how to send grin to more than one http or file address in one tx?
Gary Yu
@garyyu
@viteshan multiple receivers feature is still on the way. not supported in 1.0.x
Peter Mrekaj
@mrekucci
@ignopeverell great! Thanks.
Mark Renten
@rentenmark
hey guys, I am looking for feedback on mimblewimble/grin#2705 hashmap already mentioned something that I tackled. I would like to get this merged before the next minor release
hashmap
@hashmap
@rentenmark I added 1.0.3 milestone and merged
Mark Renten
@rentenmark
:tada: thank you sir
any idea on timing of 1.0.3 ?
hashmap
@hashmap
@rentenmark this week I think
Mark Renten
@rentenmark
oh ok nice
hashmap
@hashmap
@yeastplume what we have decided reg web wallet? We have some code to serve it in the node, do we need it?
Yeastplume
@yeastplume
it was archived a while ago, we decided to focus on the api instead and leave UI to the community
hashmap
@hashmap
@yeastplume so it’s safe to remove the corresponding code from grin itself? https://github.com/mimblewimble/grin/tree/master/servers/src/webwallet
Yeastplume
@yeastplume
yes, but I think it’s been removed in 1.1.0 branch? if not it should be removed from there
hashmap
@hashmap
ah, you are right, it’s been removed
viteshan
@viteshan
@garyyu thanks, and is there some documentation that explains the implementation about multiple receivers?
Antioch Peverell
@antiochp
we hit 100,000 blocks overnight, time for some stats -
block height: 100,087 
header MMR size: 200,162 
output MMR size: 1,456,260
rangeproof MMR size: 1,456,260 
kernel MMR size: 660,517   

outputs (approx): 728,000
UTXOs (approx): 48,000
transactions (approx): 330,000

output hash size (full unpruned): 46 MB 
output hash size on disk( pruned): 14 MB

kernel data file: 36 MB
kernel hash file: 21 MB
output data file: 4.5 MB
output hash file: 14 MB
rangeproof data file: 90 MB
rangeproof hash file: 14 MB
Quentin Le Sceller
@quentinlesceller
:rocket:
John Tromp
@tromp
:thumbsup:
Quentin Le Sceller
@quentinlesceller
is this issue mimblewimble/grin#2352 still relevant?
Mike Dallas
@mcdallas
@quentinlesceller close mimblewimble/grin#2692 too while you're at it
Quentin Le Sceller
@quentinlesceller
Done
Also not sure about mimblewimble/grin#2688 seems like a misunderstanding?
:rocket:
Mike Dallas
@mcdallas
Quentin Le Sceller
@quentinlesceller
Nice @mcdallas
lehnberg
@lehnberg
designing that in google slides… is mind blowing. I’m impressed.
Jeremy Rubin
@JeremyRubin_twitter
@antiochp can you explain how the milestone branch works. Do I need to be tracking what happens there
Antioch Peverell
@antiochp
I believe we are planning on merging into 1.1.0 branch (from master) and releasing from there, but could be mistaken - @yeastplume knows more I think
hashmap
@hashmap
@antiochp btw I removed one commit from my pr to not mess with 1.1 merge, please take a look, it would be nice to have in 1.0.3
Yeastplume
@yeastplume
yes, I’m going to have a go at merging master into 1.1.0 soon, but want to finish up current wallet v2 api first
which hopefully should just be finishing up some docs and exposing a new endpoint
Jeremy Rubin
@JeremyRubin_twitter
I guess I'm just confused as to why 1.1.0 would have conflicts with a PR opened against master
not sure what the workflow is
Ignotus Peverell
@ignopeverell
@JeremyRubin_twitter plan was to merge master into 1.1.0 a few times until it's ready, then release, then merge 1.1.0 back into master
Jeremy Rubin
@JeremyRubin_twitter
Ok. I'm just confused as to what workflow this optimises for
If I'm developing a change should I develop against master or 1.1.0
Why add to 1.1.0 at all
Is it a release feature freeze
David Burkett
@DavidBurkett
We want to be able to have small, incremental releases with bug fixes. We do that off of master. Maybe we should be using a separate branch for that?
1.1.0 is for enhancements that aren’t going to be in our frequent minor releases
Ignotus Peverell
@ignopeverell
up to the release, master should only have smaller/safer changes that can be used at pretty much anytime